List brief information of functions. Returns up to limit items. Use this first to filter targets, then fetch disassembly/decompiled code.
AI agents call list_functions 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 performs data retrieval and querying only—it lists and returns information about functions from a reverse engineering context. There are no side effects, code execution, data modification, or destructive operations. It is a Read operation with low severity since it only exposes static analysis information from a binary/executable.
From the tool's definition Tool description states it "List[s] brief information of functions" and is "Use[d] first to filter targets". The action is to retrieve and enumerate function metadata without any modification or execution of code.
Documented attack patterns abuse exactly the kind of access list_functions 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 list_functions:
{
"version": "1",
"default": "deny",
"tools": {
"list_functions": {}
}
}list_functions 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.
List brief information of functions. Returns up to limit items. Use this first to filter targets, then fetch disassembly/decompiled code. 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 list_functions: 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.
list_functions 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 list_functions 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 list_functions. 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.
list_functions 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.