Get the prototype/signature string of a function (lighter than full decompile). Returns return type, name, and parameters.
AI agents call get_function_signature to retrieve information from Kawaiidra MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a read-only retrieval of function signature information. It does not modify binary data, execute code, delete anything, or create financial obligations. Even in a binary analysis context, reading function signatures is a passive information retrieval operation.
From the tool's definition Tool explicitly retrieves function metadata: "Get the prototype/signature string of a function" and "Returns return type, name, and parameters." This is a query operation with no side effects on the binary or analysis.
Documented attack patterns abuse exactly the kind of access get_function_signature gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kawaiidra MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_function_signature:
{
"version": "1",
"default": "deny",
"tools": {
"get_function_signature": {}
}
} get_function_signature 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 the prototype/signature string of a function (lighter than full decompile). Returns return type, name, and parameters. It is categorised as a Read tool in the Kawaiidra MCP MCP Server, which means it retrieves data without modifying state.
Register the Kawaiidra MCP server in PolicyLayer and add a rule for get_function_signature: 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 Kawaiidra MCP. Nothing to install.
get_function_signature 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 get_function_signature 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 get_function_signature. 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.
get_function_signature is provided by the Kawaiidra MCP server (wagonbomb/kawaiidra-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kawaiidra MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
94 Kawaiidra MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.