Critical Risk →

clear_token_cache

Clear the stored authentication tokens.

How to control clear_token_cache ↓

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

Critical Risk

Clearing stored authentication tokens is an irreversible destructive action — once tokens are deleted, the current session/auth state is lost and cannot be undone without re-authenticating. This could disrupt an AI agent's ability to access OneNote, effectively denying service to the integration.

From the tool's definition Clear the stored authentication tokens

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

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

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

clear_token_cache 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 Onenote — 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_token_cache tool do? +

Clear the stored authentication tokens. It is categorised as a Destructive tool in the Onenote 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_token_cache? +

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

What risk level is clear_token_cache? +

clear_token_cache 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_token_cache? +

Yes. Add a rate_limit block to the clear_token_cache 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_token_cache completely? +

Set action: deny in the PolicyLayer policy for clear_token_cache. 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_token_cache? +

clear_token_cache is provided by the Onenote MCP server (purpleslurple/onenote-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Onenote tool call.

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

Free to start. No card required.

12 Onenote 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.