AI agents call clear-prompt-history to permanently remove resources in Cross-LLM MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data (prompt history/logs) without the ability to recover it. While the blast radius is somewhat contained to audit logs rather than primary application data, the irreversible nature of deletion and potential loss of important conversation records, debugging information, or compliance audit trails makes this Destructive rather than Write.
From the tool's definition Tool name explicitly includes 'clear' and description states it will 'Clear all prompt log entries' - indicating irreversible deletion of historical data.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access clear-prompt-history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cross-LLM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for clear-prompt-history:
{
"version": "1",
"default": "deny",
"hide": [
"clear-prompt-history"
]
}clear-prompt-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 all prompt log entries. It is categorised as a Destructive tool in the Cross-LLM MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Cross-LLM MCP Server MCP server in PolicyLayer and add a rule for clear-prompt-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 Cross-LLM MCP Server. Nothing to install.
clear-prompt-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-prompt-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-prompt-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-prompt-history is provided by the Cross-LLM MCP Server MCP server (jamesanz/cross-llm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cross-LLM MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
23 Cross-LLM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.