Critical Risk →

clear_auth

Clear the authentication token and log out of Trakt

How to control clear_auth ↓

AI agents call clear_auth to permanently remove resources in Trakt — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Clearing an authentication token is an irreversible action that terminates the current session and removes stored credentials. The user would need to re-authenticate to regain access. This cannot be undone automatically and constitutes a destructive action on the auth state, though its blast radius is limited to session disruption rather than data loss.

From the tool's definition Clear the authentication token and log out of Trakt

Documented attack patterns abuse exactly the kind of access clear_auth gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Trakt, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_auth:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear_auth"
  ]
}

clear_auth disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Trakt — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the clear_auth tool do? +

Clear the authentication token and log out of Trakt. It is categorised as a Destructive tool in the Trakt MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on clear_auth? +

Register the Trakt MCP server in PolicyLayer and add a rule for clear_auth: 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 Trakt. Nothing to install.

What risk level is clear_auth? +

clear_auth is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit clear_auth? +

Yes. Add a rate_limit block to the clear_auth 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.

How do I block clear_auth completely? +

Set action: deny in the PolicyLayer policy for clear_auth. 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.

What MCP server provides clear_auth? +

clear_auth is provided by the Trakt MCP server (wwiens/trakt_mcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Trakt tool call.

Deterministic rules across all 77 Trakt tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

77 Trakt tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.