AI agents invoke callgraph 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.
The tool performs an active operation (graph building/analysis) rather than simple retrieval. The high severity reflects that an agent could trigger computationally expensive operations or generate voluminous output by specifying large root function sets, potentially causing resource exhaustion or DoS conditions against the IDA Pro analysis environment.
From the tool's definition Tool performs 'Build call graph starting from root functions' - this is a computational operation that traverses and analyzes function call relationships in a binary, which requires executing analysis algorithms on the IDA Pro database.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access callgraph 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 callgraph:
{
"version": "1",
"default": "deny",
"tools": {
"callgraph": {
"limits": [
{
"counter": "callgraph_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}callgraph 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.
Build call graph starting from root functions. 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 callgraph: 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.
callgraph 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 callgraph 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 callgraph. 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.
callgraph 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.