Execute core debugger actions (run, pause, step, state, etc.)
Part of the X64dbg server.
Free to start. No card required.
AI agents invoke x64dbg_debug to trigger processes or run actions in X64dbg. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
x64dbg_debug can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"x64dbg_debug": {
"limits": [
{
"counter": "x64dbg_debug_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full X64dbg policy for all 23 tools.
These attack patterns abuse exactly the kind of access x64dbg_debug gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Execute core debugger actions (run, pause, step, state, etc.). It is categorised as a Execute tool in the X64dbg MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the X64dbg MCP server in PolicyLayer and add a rule for x64dbg_debug: 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. Nothing to install.
x64dbg_debug is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the x64dbg_debug 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 x64dbg_debug. 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.
x64dbg_debug is provided by the X64dbg MCP server (x64dbg-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 23 X64dbg tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.