AI agents call disasm to retrieve information from Ida Domain without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Disassembly retrieves and displays machine code in human-readable form without modifying the underlying database or binary. Consistent with sibling tools that query/analyze program structure. Low severity because it only accesses existing analysis data with no side effects. Confidence reduced slightly due to missing description, but the name and context strongly indicate a read operation.
From the tool's definition Tool name 'disasm' (disassembly) from an IDA Pro analysis server; context shows read-only analysis tools (analyze_funcs, analyze_strings, basic_blocks, callgraph, callers, callees).
Documented attack patterns abuse exactly the kind of access disasm 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 disasm:
{
"version": "1",
"default": "deny",
"tools": {
"disasm": {}
}
} disasm is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
disasm. It is categorised as a Read tool in the Ida Domain MCP Server, which means it retrieves data without modifying state.
Register the Ida Domain MCP server in PolicyLayer and add a rule for disasm: 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.
disasm is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the disasm 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 disasm. 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.
disasm 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.