Disassemble instructions starting at an address or symbol.
AI agents call disassemble to retrieve information from x64dbg MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Disassembly is a fundamental reverse-engineering read operation that queries and presents binary code in human-readable form. It has no side effects—it does not modify the debugged process, execute code, delete data, or commit any irreversible changes. While it requires the debugger to be attached to a process, the tool itself only reads and analyzes memory contents.
From the tool's definition Tool performs disassembly analysis starting at an address or symbol, which retrieves and displays machine code instructions without modifying executable state or triggering execution.
Attacks that exploit this kind of access
Disassemble instructions starting at an address or symbol. It is categorised as a Read tool in the x64dbg MCP Server MCP Server, which means it retrieves data without modifying state.
Register the x64dbg MCP Server MCP server in PolicyLayer and add a rule for disassemble: 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.
disassemble 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 disassemble 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 disassemble. 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.
disassemble 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →