Get detailed structured information of a single function (address, size, xrefs, etc.). Pass the hexadecimal address string.
AI agents call function_detail 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 queries and returns metadata about functions in a binary without executing code, modifying data, or causing side effects. It is analogous to inspecting static analysis results. The blast radius of misuse is minimal—the AI agent can only retrieve existing information about the target binary. No data is created, modified, deleted, or executed.
From the tool's definition Tool description states 'Get detailed structured information of a single function (address, size, xrefs, etc.)' — purely retrieval/query operation with no modification capability.
Documented attack patterns abuse exactly the kind of access function_detail 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 function_detail:
{
"version": "1",
"default": "deny",
"tools": {
"function_detail": {}
}
}function_detail 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.
Get detailed structured information of a single function (address, size, xrefs, etc.). Pass the hexadecimal address string. 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 function_detail: 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.
function_detail 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 function_detail 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 function_detail. 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.
function_detail 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.