Remove an action map from an Input Action Asset.
AI agents call unity_input_remove_map to permanently remove resources in Unity MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing an action map from an Input Action Asset destroys project configuration that cannot be automatically undone. While not a database DROP or force-push, it permanently deletes structured game input configuration. An AI agent could accidentally remove critical input mappings (e.g., player controls), breaking gameplay.
From the tool's definition Tool name contains 'remove' and description states 'Remove an action map from an Input Action Asset' — this operation irreversibly deletes configuration data from a Unity project asset.
Documented attack patterns abuse exactly the kind of access unity_input_remove_map gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Unity MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for unity_input_remove_map:
{
"version": "1",
"default": "deny",
"hide": [
"unity_input_remove_map"
]
} unity_input_remove_map disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove an action map from an Input Action Asset. It is categorised as a Destructive tool in the Unity MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Unity MCP Server MCP server in PolicyLayer and add a rule for unity_input_remove_map: 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 Unity MCP Server. Nothing to install.
unity_input_remove_map is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the unity_input_remove_map 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 unity_input_remove_map. 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.
unity_input_remove_map is provided by the Unity MCP Server MCP server (anklebreaker-studio/unity-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Unity MCP Server, 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.
324 Unity MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.