unity_advanced_tool
Execute an advanced Unity tool by name (${advanced.length} cached + plugin lazy-loaded;
This record as markdown: /tools/anklebreaker-studio-unity-mcp-server/unity-advanced-tool.md
What unity_advanced_tool does on Unity MCP Server
AI agents invoke unity_advanced_tool to trigger actions in Unity MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why unity_advanced_tool is rated High
This is an Execute category risk because it dynamically executes Unity tools by name, allowing an AI agent to invoke arbitrary advanced operations whose effects depend on the tool name argument. While not explicitly destructive or financial, the ability to execute arbitrary advanced Unity operations (potentially including builds, asset manipulation, scene changes, etc.) represents a high blast radius if misused.
From the tool's definition The tool name is 'unity_advanced_tool' and the description states 'Execute an advanced Unity tool by name' — the verb 'Execute' directly indicates the tool runs code or triggers external operations.
Attacks that exploit this kind of access
The rule that runs unity_advanced_tool 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_advanced_tool, this is the rule to start with:
unity_advanced_tool stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_advanced_tool call is checked against it from then on.
Questions about unity_advanced_tool
Execute an advanced Unity tool by name (${advanced.length} cached + plugin lazy-loaded;. It is categorised as a Execute tool in the Unity MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Unity MCP Server MCP server in PolicyLayer and add a rule for unity_advanced_tool: 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_advanced_tool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the unity_advanced_tool 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_advanced_tool. 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_advanced_tool 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.
Across the catalogue