AI agents use rename_local_variable to create or update resources in CutterMCP-plus — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CutterMCP-plus environment.
This tool modifies metadata within a Cutter reverse engineering project by renaming local variables/parameters. While the change is reversible (names can be renamed again), it alters the state of an analysis project and could impact reproducibility or understanding of decompiled code if misused. It does not execute external code, delete irreversible data, or move money, so Write is the appropriate category.
From the tool's definition Tool name 'rename_local_variable' and description 'Rename local variable/parameter' indicate modification of reversing project metadata (variable names in analysis context).
Documented attack patterns abuse exactly the kind of access rename_local_variable 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 rename_local_variable:
{
"version": "1",
"default": "deny",
"tools": {
"rename_local_variable": {
"limits": [
{
"counter": "rename_local_variable_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}rename_local_variable 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 local variable/parameter. It is categorised as a Write tool in the CutterMCP-plus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CutterMCP-plus MCP server in PolicyLayer and add a rule for rename_local_variable: 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.
rename_local_variable 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_local_variable 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_local_variable. 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_local_variable 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.