A shared task list lets an AI agent help with planning without moving your work into another system. The important decision is not simply whether to connect an agent, but what that connection is allowed to read or change.
Least privilege means granting no more access than a workflow needs. In TaskPort, that starts with understanding the current permission boundary, choosing a read-only connection where possible, and keeping each agent’s credentials separate.
Understand what a TaskPort token permits
TaskPort tokens belong to one account, not to selected lists. The current permission choices are Read Only and Read & Write. The list_lists tool returns the lists owned by the connected account.
A list_id filter tells a tool which list to retrieve; it is not an authorization restriction. Creating an “Agent Inbox” or asking an agent to ignore a personal list does not prevent its token from accessing other lists in the same account.
Read Only prevents task changes, but it still permits reading account content through the available tools. Before connecting, consider whether the agent should be able to access the account’s task titles, notes and attachments. Keep information it should never receive outside that connected account. See the current TaskPort permission model before issuing a token.
Start with a read-only planning workflow
A morning review is a useful first connection because it does not require changing tasks. The agent can summarize upcoming work while you decide what to complete or reschedule in TaskPort.
- In TaskPort, open Settings, then Manage Agent Access, and create a new agent with Read Only access.
- Store its one-time token in your MCP client’s supported secret settings, not in a prompt or shared document.
- Configure the remote connection using Streamable HTTP and bearer authorization.
- Ask the agent to call
list_lists. Check that the returned names belong to the account you intended to connect. - Select a list and request a read-only summary of its open tasks.
A first request can be:
Use TaskPort to show the lists in my connected account.
Then summarize the open tasks in the list I choose.
Do not create, update or delete anything.The instruction makes your intent clear; the Read Only token is what prevents write operations. An empty task list can be a valid response and should not be confused with a failed connection. Follow the first-connection walkthrough for configuration and checks.
Use write access deliberately
Read & Write is appropriate only when the agent needs to modify work. It includes operations that create, update and permanently delete tasks or lists. That authority applies across the connected account, not just the list named in your request.
TaskPort does not currently require a separate human approval before every write. Any approval prompts must come from your agent client or workflow. Do not assume they exist without checking the client’s behavior.
An Agent Inbox can still be useful for organizing proposed tasks. You can ask a write-enabled agent to put suggestions there, then review them before moving them into your plan. Treat this as an operating convention, not a technical barrier protecting the rest of the account.
If you need suggestions without accepting that write access, keep the token Read Only. Let the agent propose changes in its response and make the edits yourself.
Keep credentials separate and review them
Create a distinct, recognizable token for each agent connection. Separate credentials let you revoke one connection without also disconnecting another agent. Record the purpose and permission level, but do not copy the token itself into that record.
Review active connections when a project ends or an agent’s role changes. Revoke credentials you no longer need or suspect have been exposed. Revocation stops future authenticated requests; it does not undo previous changes or erase information the agent already received.
A practical least-privilege checklist
- Check whether the agent may read the entire connected account
- Start with Read Only for summaries and planning
- Use separate credentials for separate connections
- Keep secrets and unnecessary sensitive details out of task content
- Verify client approval behavior before granting write access
- Review changes and revoke unused connections
A reliable shared workflow needs both clear instructions and accurately understood permissions. Use TaskPort’s existing controls for what they enforce, and do not mistake an organizational pattern for an access restriction.
