AI agents invoke dbg_run_to to trigger actions in Ida Domain. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a debugger action that controls program flow and execution. While it doesn't create, modify, or delete persistent data (Write/Destructive), it does trigger execution of code in an external process (the debugged program). The effects are contingent on the supplied address argument, making it Execute rather than Read.
From the tool's definition Tool name 'dbg_run_to' and description 'Run to address' indicate execution of a debugger command that resumes program execution until a specified address is reached.
Documented attack patterns abuse exactly the kind of access dbg_run_to gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ida Domain, and nothing reaches the server without passing your rules. This is the rule we recommend for dbg_run_to:
{
"version": "1",
"default": "deny",
"tools": {
"dbg_run_to": {
"limits": [
{
"counter": "dbg_run_to_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}dbg_run_to stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Run to address. It is categorised as a Execute tool in the Ida Domain MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ida Domain MCP server in PolicyLayer and add a rule for dbg_run_to: 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 Ida Domain. Nothing to install.
dbg_run_to 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 dbg_run_to 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 dbg_run_to. 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.
dbg_run_to is provided by the Ida Domain MCP server (xxyyue/ida_domain_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ida Domain, 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.
74 Ida Domain tools catalogued and risk-classified — across an index of 43,000+ MCP servers.