Update the contents of an existing C# script file.
AI agents use unity_script_update 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 modifies script files reversibly (existing C# scripts can be edited, versions controlled, or reverted). While it doesn't delete data, it can change critical game logic, asset references, and application behavior. The high severity reflects the potential for an AI agent to inadvertently corrupt game logic, break dependencies, or introduce security vulnerabilities in production code.
From the tool's definition Tool name 'unity_script_update' and description 'Update the contents of an existing C# script file' directly indicate modification of existing code files.
Documented attack patterns abuse exactly the kind of access unity_script_update 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_script_update:
{
"version": "1",
"default": "deny",
"tools": {
"unity_script_update": {
"limits": [
{
"counter": "unity_script_update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} unity_script_update 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.
Update the contents of an existing C# script file. 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_script_update: 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_script_update 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_script_update 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_script_update. 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_script_update 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.