Wire multiple object references in a single call. Efficient for setting up many references at once (e.g. wiring a UI manager to all its panels, connecting enemy AI to patrol waypoints). Each entry specifies a target GameObject, property, and reference to assign.
AI agents use unity_component_batch_wire 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.
This tool creates or modifies data (object property assignments in a game scene) reversibly. While it affects multiple targets efficiently, these changes can be undone through standard Unity undo operations. The severity is high due to the batch nature allowing mass modifications that could break scene functionality if misused, but it does not execute arbitrary code, delete data, or cause financial impact.
From the tool's definition Tool description states it 'wires multiple object references' and 'setting up many references', which modifies GameObject properties in Unity scenes. The batch operation nature means high blast radius.
Documented attack patterns abuse exactly the kind of access unity_component_batch_wire 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_component_batch_wire:
{
"version": "1",
"default": "deny",
"tools": {
"unity_component_batch_wire": {
"limits": [
{
"counter": "unity_component_batch_wire_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}unity_component_batch_wire 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.
Wire multiple object references in a single call. Efficient for setting up many references at once (e.g. wiring a UI manager to all its panels, connecting enemy AI to patrol waypoints). Each entry specifies a target GameObject, property, and reference to assign. 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_component_batch_wire: 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_component_batch_wire 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_component_batch_wire 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_component_batch_wire. 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_component_batch_wire 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.