Load/activate a specific scenario by its asset path.
AI agents invoke unity_mppm_activate_scenario 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.
Activating/loading a scenario triggers external operations in the Unity Editor (changing the active scenario state), which goes beyond simple data retrieval or writing. It executes a state change in the runtime environment. Severity is medium as misuse could disrupt the active project state but is generally reversible.
From the tool's definition Load/activate a specific scenario by its asset path
Documented attack patterns abuse exactly the kind of access unity_mppm_activate_scenario 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_mppm_activate_scenario:
{
"version": "1",
"default": "deny",
"tools": {
"unity_mppm_activate_scenario": {
"limits": [
{
"counter": "unity_mppm_activate_scenario_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} unity_mppm_activate_scenario 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.
Load/activate a specific scenario by its asset path. 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_mppm_activate_scenario: 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_mppm_activate_scenario 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_mppm_activate_scenario 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_mppm_activate_scenario. 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_mppm_activate_scenario 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.