Clear stored OAuth tokens (access + refresh). Personal API token configured via env or file is unaffected.
AI agents call kanka_auth_logout to permanently remove resources in Kanka — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing OAuth tokens is irreversible in the sense that the stored credentials are permanently deleted from local storage, requiring re-authentication to restore access. This cannot be undone without going through the OAuth login flow again. While it doesn't delete campaign data, it destroys authentication state, potentially disrupting ongoing agent operations.
From the tool's definition Clear stored OAuth tokens (access + refresh)
Attacks that exploit this kind of access
Clear stored OAuth tokens (access + refresh). Personal API token configured via env or file is unaffected. It is categorised as a Destructive tool in the Kanka MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Kanka MCP server in PolicyLayer and add a rule for kanka_auth_logout: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Kanka. Nothing to install.
kanka_auth_logout is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the kanka_auth_logout rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for kanka_auth_logout. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
kanka_auth_logout is provided by the Kanka MCP server (torinvdb/kanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →