Install additional platform modules to an already-installed Unity Editor version.
AI agents invoke unity_hub_install_modules 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.
Installing software modules triggers external operations that modify the Unity installation environment. This is not a simple write (it runs installation processes), and while it could be partially reversed by uninstalling, the act of installing software and modifying a development environment is best classified as Execute with high severity due to the blast radius of installing unwanted or malicious modules into…
From the tool's definition Install additional platform modules to an already-installed Unity Editor version
Documented attack patterns abuse exactly the kind of access unity_hub_install_modules 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_hub_install_modules:
{
"version": "1",
"default": "deny",
"tools": {
"unity_hub_install_modules": {
"limits": [
{
"counter": "unity_hub_install_modules_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} unity_hub_install_modules 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.
Free to start. No card required.
Install additional platform modules to an already-installed Unity Editor version. 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_hub_install_modules: 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_hub_install_modules 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_hub_install_modules 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_hub_install_modules. 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_hub_install_modules 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.
Deterministic rules across all 324 Unity MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
324 Unity MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.