Critical Risk →

clear_thinking_history

Clear all recorded thoughts and reset the server state.

How to control clear_thinking_history ↓

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

Critical Risk

An AI agent that decides to call clear_thinking_history doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Mcp Structured Thinking is gone — there is no undo for destructive operations.

Risk signalsBulk/mass operation — affects multiple targets

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

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

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

clear_thinking_history 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 Mcp Structured Thinking — 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_thinking_history tool do? +

Clear all recorded thoughts and reset the server state. It is categorised as a Destructive tool in the Mcp Structured Thinking 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_thinking_history? +

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

What risk level is clear_thinking_history? +

clear_thinking_history 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_thinking_history? +

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

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

clear_thinking_history is provided by the Mcp Structured Thinking MCP server (promptly-technologies-llc/mcp-structured-thinking). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Structured Thinking tool call.

Deterministic rules across all 5 Mcp Structured Thinking tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

5 Mcp Structured Thinking 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.