An MCP client can read and, when your role permits, change Taskavel work as the connected user. Treat an OAuth connection or personal access token as an account credential, not as a convenience setting to paste into a chat or repository. The practical safeguard is a combination of private credential storage, narrow prompts, and regular review.
Keep credentials private
Store a personal access token only in the designated client’s secret configuration or in an environment variable managed by your operating system or secret manager. Do not commit it to source control, put it in a project-level file shared with a team, include it in screenshots, or send it through support chat. Create a separately named token for each client or machine so that revocation has a small, clear blast radius.
OAuth avoids handing a raw token to a browser connector, but it still deserves review. Complete approval only after confirming the intended Taskavel account in the browser. If you use shared devices or multiple accounts, verify the account before approving a new connection.
Ask for explicit, reviewable actions
Begin with read tools. Ask an agent to list projects, inspect a task, show a board snapshot, or explain what it found before asking it to write. For a mutation, identify the target and result: project, task, destination column, comment text, or milestone. A client should pause for ambiguity instead of guessing.
Use an additional confirmation point for consequential actions. Archiving is safer than permanent deletion when you are not certain; Taskavel only permits permanent deletion of an already archived task and requires explicit confirmation in the tool call. Avoid blanket instructions such as “delete old tasks” unless you have first reviewed the exact set.
Revoke the correct access path
Open Account Settings → AI Integration (MCP). Connected OAuth clients and personal access tokens appear in different lists. Choose Disconnect to revoke an OAuth client. Revoke the named PAT to stop a CLI or local agent that uses Bearer authentication. One operation does not cancel the other, so inspect both lists after a machine is lost, a client is retired, or a credential may have been exposed.
If a PAT may have leaked, revoke it before investigating or reconfiguring the client. Create a replacement only after you have removed the exposed value from the client configuration and verified the new storage location. Then validate the replacement with a read-only request.
For the account and role boundary behind these controls, see permissions and project scope.