Clear conversation history for a specific AI model or all models
AI agents call clear_conversation_history to permanently remove resources in Second Opinion MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (conversation history). While the blast radius is limited compared to system-wide deletions, the data loss is permanent and unrecoverable. This meets the definition of Destructive rather than Write (which is reversible).
From the tool's definition Tool name explicitly uses 'clear' which indicates irreversible deletion. Description states 'Clear conversation history' without qualification or undo capability. The action permanently removes accumulated conversation data that cannot be recovered.
Documented attack patterns abuse exactly the kind of access clear_conversation_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Second Opinion MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_conversation_history:
{
"version": "1",
"default": "deny",
"hide": [
"clear_conversation_history"
]
} clear_conversation_history disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Clear conversation history for a specific AI model or all models. It is categorised as a Destructive tool in the Second Opinion MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Second Opinion MCP server in PolicyLayer and add a rule for clear_conversation_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 Second Opinion MCP. Nothing to install.
clear_conversation_history 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 clear_conversation_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.
Set action: deny in the PolicyLayer policy for clear_conversation_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.
clear_conversation_history is provided by the Second Opinion MCP server (procreations-official/second-opinion). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Second Opinion MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 Second Opinion MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.