AI agents use rename_function to create or update resources in Kawaiidra MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kawaiidra MCP environment.
This tool modifies metadata (function names) within a binary analysis project reversibly—renames can be undone or changed again. This is a Write operation: it creates or modifies data without permanently destroying information or executing external operations. The modification is confined to the analysis project itself, not to the original binary or production systems, limiting blast radius to medium severity.
From the tool's definition Tool name 'rename_function' and description 'Rename a function in the binary analysis' indicate modification of function metadata within a binary analysis context (Ghidra project).
Documented attack patterns abuse exactly the kind of access rename_function 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 rename_function:
{
"version": "1",
"default": "deny",
"tools": {
"rename_function": {
"limits": [
{
"counter": "rename_function_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}rename_function stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Rename a function in the binary analysis. It is categorised as a Write tool in the Kawaiidra MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kawaiidra MCP server in PolicyLayer and add a rule for rename_function: 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.
rename_function is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the rename_function 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 rename_function. 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.
rename_function 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.