Disassemble the entire function as text (pdf) given its address. Recommended, but be cautious of large functions. If this fails, try disasm_text.
AI agents call disasm_by_func_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 is a read-only tool that performs static analysis and retrieves data from an already-loaded binary. It does not execute code, modify binaries, delete data, or trigger external operations. Even though reverse engineering can inform malicious acts, the tool itself is purely informational—it queries and returns existing disassembly information. Low severity reflects the benign nature of the operation itself.
From the tool's definition The tool 'disasm_by_func_text' retrieves disassembled function code as text output. The description states it 'disassemble[s] the entire function as text' and explicitly recommends caution for large functions—indicating it is a retrieval/analysis operation…
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access disasm_by_func_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_by_func_text:
{
"version": "1",
"default": "deny",
"tools": {
"disasm_by_func_text": {}
}
}disasm_by_func_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.
Disassemble the entire function as text (pdf) given its address. Recommended, but be cautious of large functions. If this fails, try disasm_text. 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_by_func_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_by_func_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_by_func_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_by_func_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_by_func_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.