Install/update Unity MCP bridge scripts to a Unity project (works even if Unity server is not running)
AI agents use setup_unity_bridge to create or update resources in MCP Server for Unity — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Server for Unity environment.
This tool creates or modifies bridge scripts within a Unity project, which are reversible operations (scripts can be deleted or updated). While it affects the project state, it does not irreversibly destroy data or execute arbitrary commands within the project context itself—it merely installs/updates specific bridge infrastructure files. This is a Write-class operation.
From the tool's definition Tool description states 'Install/update Unity MCP bridge scripts to a Unity project', indicating creation and modification of project files.
Documented attack patterns abuse exactly the kind of access setup_unity_bridge gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server for Unity, and nothing reaches the server without passing your rules. This is the rule we recommend for setup_unity_bridge:
{
"version": "1",
"default": "deny",
"tools": {
"setup_unity_bridge": {
"limits": [
{
"counter": "setup_unity_bridge_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} setup_unity_bridge 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.
Install/update Unity MCP bridge scripts to a Unity project (works even if Unity server is not running). It is categorised as a Write tool in the MCP Server for Unity MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Server for Unity MCP server in PolicyLayer and add a rule for setup_unity_bridge: 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 MCP Server for Unity. Nothing to install.
setup_unity_bridge 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 setup_unity_bridge 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 setup_unity_bridge. 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.
setup_unity_bridge is provided by the MCP Server for Unity MCP server (zabaglione/mcp-server-unity). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Server for Unity, 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.
15 MCP Server for Unity tools catalogued and risk-classified — across an index of 43,000+ MCP servers.