AI agents use manage_control_schemes to create or update resources in Unity — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unity environment.
An AI agent can call manage_control_schemes faster than any human can review — one bad instruction and it creates or modifies resources in Unity by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Manage Control Schemes in an Input Actions asset. It is categorised as a Write tool in the Unity MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Unity MCP server in PolicyLayer and add a rule for manage_control_schemes: 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. Nothing to install.
manage_control_schemes 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 manage_control_schemes 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 manage_control_schemes. 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.
manage_control_schemes is provided by the Unity MCP server (@akiojin/unity-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.