Critical Risk →

unity_input_remove_action

Remove an action (and its bindings) from an action map.

How to control unity_input_remove_action ↓

AI agents call unity_input_remove_action 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.

Critical Risk

This tool irreversibly removes an input action and all its bindings from an action map. Deletion of input actions cannot be trivially undone and could break game functionality that depends on those bindings. This qualifies as Destructive due to the permanent removal of configuration data.

From the tool's definition 'Remove an action (and its bindings) from an action map' — permanently deletes an action along with all its associated bindings

Documented attack patterns abuse exactly the kind of access unity_input_remove_action 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_action:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "unity_input_remove_action"
  ]
}

unity_input_remove_action disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Unity MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the unity_input_remove_action tool do? +

Remove an action (and its bindings) from an action map. 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.

How do I enforce a policy on unity_input_remove_action? +

Register the Unity MCP Server MCP server in PolicyLayer and add a rule for unity_input_remove_action: 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.

What risk level is unity_input_remove_action? +

unity_input_remove_action is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit unity_input_remove_action? +

Yes. Add a rate_limit block to the unity_input_remove_action 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.

How do I block unity_input_remove_action completely? +

Set action: deny in the PolicyLayer policy for unity_input_remove_action. 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.

What MCP server provides unity_input_remove_action? +

unity_input_remove_action 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.

Enforce policy on every Unity MCP Server tool call.

Deterministic rules across all 324 Unity MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

324 Unity MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.