AI agents use set_local_variable_type 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 data (variable type metadata) within Cutter's reverse engineering environment. It is a Write operation as it changes an annotation/metadata reversibly within the session. Misuse could corrupt analysis but is not inherently destructive or irreversible at a system level.
From the tool's definition 'Set local variable type' — modifies the type annotation of a local variable in the reverse engineering session
Documented attack patterns abuse exactly the kind of access set_local_variable_type 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 set_local_variable_type:
{
"version": "1",
"default": "deny",
"tools": {
"set_local_variable_type": {
"limits": [
{
"counter": "set_local_variable_type_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_local_variable_type 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.
Set local variable type. 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 set_local_variable_type: 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.
set_local_variable_type 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 set_local_variable_type 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 set_local_variable_type. 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.
set_local_variable_type 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.