unity_input_add_binding
Add a simple (non-composite) binding to an action. Use for single-key bindings like
This record as markdown: /tools/anklebreaker-studio-unity-mcp-server/unity-input-add-binding.md
What unity_input_add_binding does on Unity MCP Server
AI agents use unity_input_add_binding to create or update resources in Unity MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unity MCP Server environment.
Why unity_input_add_binding is rated Medium
This tool creates or modifies input binding configurations in Unity's input system. While the change is reversible (bindings can be removed or reassigned), it affects application behavior and could disrupt game controls if misconfigured by an agent. It does not execute arbitrary code, delete data irreversibly, or move money, making Write the appropriate category.
From the tool's definition Tool name 'unity_input_add_binding' and description 'Add a simple (non-composite) binding to an action' indicates creation/modification of input configuration data. The verb 'Add' and context of binding configuration demonstrates reversible data modification.
Attacks that exploit this kind of access
The rule that runs unity_input_add_binding safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unity MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unity_input_add_binding, this is the rule to start with:
unity_input_add_binding 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Unity MCP Server, apply this rule, and every unity_input_add_binding call is checked against it from then on.
Questions about unity_input_add_binding
Add a simple (non-composite) binding to an action. Use for single-key bindings like. It is categorised as a Write tool in the Unity MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Unity MCP Server MCP server in PolicyLayer and add a rule for unity_input_add_binding: 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_add_binding 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 unity_input_add_binding 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_add_binding. 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_add_binding 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.
More on Unity MCP Server, and thousands of servers like it.
This server
Across the catalogue