Permanently delete a saved context. Use when the user says
AI agents call bridge_delete_context to permanently remove resources in Acheron — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool destroys stored data without recovery options. Although the data is user-owned (not system-critical), permanent deletion of user context memories represents an irreversible operation with potentially significant blast radius if triggered by an AI agent misinterpreting user intent.
From the tool's definition Tool name includes 'delete' and description states 'Permanently delete a saved context' — irreversible data removal.
Documented attack patterns abuse exactly the kind of access bridge_delete_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Acheron, and nothing reaches the server without passing your rules. This is the rule we recommend for bridge_delete_context:
{
"version": "1",
"default": "deny",
"hide": [
"bridge_delete_context"
]
}bridge_delete_context 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.
Permanently delete a saved context. Use when the user says. It is categorised as a Destructive tool in the Acheron MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Acheron MCP server in PolicyLayer and add a rule for bridge_delete_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 Acheron. Nothing to install.
bridge_delete_context 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 bridge_delete_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.
Set action: deny in the PolicyLayer policy for bridge_delete_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.
bridge_delete_context is provided by the Acheron MCP server (timmx7/acheron-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Acheron, 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.
6 Acheron tools catalogued and risk-classified — across an index of 43,000+ MCP servers.