Linear disassembly in JSON format. Returns {addr, count, ops:[...]}. Default 64 ops.
AI agents call disasm_json to retrieve information from CutterMCP-plus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries disassembly information from a binary analysis tool. It has no side effects—it does not modify code, execute anything, delete data, or trigger external operations. The output is purely informational. While reverse engineering tools can be used maliciously, the tool itself is strictly read-only and falls cleanly into the Read category.
From the tool's definition Tool returns disassembly output in JSON format ('{addr, count, ops:[...]}') with no modification, deletion, or execution capabilities. The description explicitly indicates a read-only retrieval of disassembly data.
Documented attack patterns abuse exactly the kind of access disasm_json gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CutterMCP-plus, and nothing reaches the server without passing your rules. This is the rule we recommend for disasm_json:
{
"version": "1",
"default": "deny",
"tools": {
"disasm_json": {}
}
}disasm_json 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.
Linear disassembly in JSON format. Returns {addr, count, ops:[...]}. Default 64 ops. It is categorised as a Read tool in the CutterMCP-plus MCP Server, which means it retrieves data without modifying state.
Register the CutterMCP-plus MCP server in PolicyLayer and add a rule for disasm_json: 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 CutterMCP-plus. Nothing to install.
disasm_json 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_json 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_json. 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_json is provided by the CutterMCP-plus MCP server (restkhz/cuttermcp-plus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 20 CutterMCP-plus tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
20 CutterMCP-plus tools catalogued and risk-classified — across an index of 42,500+ MCP servers.