clear_user_context

THE RISK

Critical Risk

Why clear_user_context needs a policy

This tool irreversibly clears all stored user context values and resets the persistent store to empty. The action is destructive because it wipes all persistent state that may have been accumulated, with no indication of recovery or undo capability.

From the tool's definition Clear all stored user context values. Resets the persistent store to empty.

Risk signalsBulk/mass operation — affects multiple targets

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

POLICY

How to control clear_user_context

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear_user_context"
  ]
}

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

Create a free account and register Pane — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Pane tools

Destructive reset Reset the display to initial state (cancels pending input) Execute execute_action Execute an action to change the app state. Must be one of the available actions from get_c Execute toggle_sidebar Toggle the sidebar visibility Write append Append content to the current display Write show_input_form Display an input form to the user and request their input. Returns immediately - use get_u Write show_multi_form Display a multi-field form to collect multiple inputs at once. All field values are stored Write undo Undo the last change Write set_markdown Set the displayed content to markdown

All 15 Pane tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Pane → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about clear_user_context

What does the clear_user_context tool do? +

Clear all stored user context values. Resets the persistent store to empty. It is categorised as a Destructive tool in the Pane 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_user_context? +

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

What risk level is clear_user_context? +

clear_user_context 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_user_context? +

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

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

clear_user_context is provided by the Pane MCP server (zabaca/pane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pane tool call.

Start from Pane, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →