AI agents call delete_session to permanently remove resources in Binary MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool destructively removes user-created session artifacts (likely Ghidra, x64dbg, or WinDbg debug sessions) without reversibility. While the blast radius is limited to analytical sessions rather than production systems, the loss of detailed debugging work and analysis state qualifies as high-severity destructive action. An AI agent tricked into deleting sessions could lose hours of analysis effort.
From the tool's definition 'Delete a saved session' — the tool irreversibly removes stored session data with no undo mechanism mentioned.
Documented attack patterns abuse exactly the kind of access delete_session gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Binary MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_session:
{
"version": "1",
"default": "deny",
"hide": [
"delete_session"
]
}delete_session 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.
Delete a saved session. It is categorised as a Destructive tool in the Binary MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Binary MCP Server MCP server in PolicyLayer and add a rule for delete_session: 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 Binary MCP Server. Nothing to install.
delete_session 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 delete_session 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 delete_session. 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.
delete_session is provided by the Binary MCP Server MCP server (sarks0/binary-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Binary 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.
59 Binary MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.