実行履歴をクリア
AI agents call clear_execution_history to permanently remove resources in MCP Claude Context Continuity — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes execution history records without a reversibility mechanism or undo capability. While the blast radius is primarily limited to session metadata rather than application data or financial systems, the permanent deletion of audit/history information qualifies as Destructive. It exceeds Write severity because deletion is irreversible.
From the tool's definition clear_execution_history irreversibly deletes execution history data. The Japanese description '実行履歴をクリア' translates to 'clear execution history', confirming it removes records that cannot be recovered.
Attacks that exploit this kind of access
実行履歴をクリア. It is categorised as a Destructive tool in the MCP Claude Context Continuity MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Claude Context Continuity MCP server in PolicyLayer and add a rule for clear_execution_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 Claude Context Continuity. Nothing to install.
clear_execution_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_execution_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_execution_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_execution_history is provided by the MCP Claude Context Continuity MCP server (tethiro/mcp-claude-context-continuity). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →