Terminate all sessions and kill all tracked x64dbg/x32dbg processes.
AI agents call close_debugger to permanently remove resources in x64dbg MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly terminates all active debugger sessions and kills processes. Killing processes is an irreversible action — any unsaved state, analysis, or in-memory data is lost. This qualifies as Destructive given the permanent, unrecoverable nature of process termination.
From the tool's definition Terminate all sessions and kill all tracked x64dbg/x32dbg processes
Attacks that exploit this kind of access
Terminate all sessions and kill all tracked x64dbg/x32dbg processes. It is categorised as a Destructive tool in the x64dbg MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the x64dbg MCP Server MCP server in PolicyLayer and add a rule for close_debugger: 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 x64dbg MCP Server. Nothing to install.
close_debugger 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 close_debugger 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 close_debugger. 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.
close_debugger is provided by the x64dbg MCP Server MCP server (ouonet/x64dbg-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
close_debugger is one line of x64dbg MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →