Linear disassembly text: from addr, list count instructions, default 64. Can be used as a fallback when disasm_by_func_text fails.
AI agents call disasm_text 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 displays assembly-level instructions from a binary file starting at a specified address. It is a query operation with no side effects—it reads static analysis data without altering the binary, executing code, or modifying any state. The worst outcome of misuse is information disclosure about the target binary's instructions, which is a read-level risk.
From the tool's definition Tool performs disassembly retrieval from a binary analysis tool (Cutter). Description states it "list[s] count instructions" and serves as a fallback for disassembly output. Key verbs are read-only: 'disassembly', 'list'.
Documented attack patterns abuse exactly the kind of access disasm_text 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_text:
{
"version": "1",
"default": "deny",
"tools": {
"disasm_text": {}
}
}disasm_text 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 text: from addr, list count instructions, default 64. Can be used as a fallback when disasm_by_func_text fails. 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_text: 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_text 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_text 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_text. 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_text 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.