Open a specified scene in the Unity editor.
AI agents invoke open_scene to trigger actions in Unity MCP with Ollama Integration. 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.
Opening a scene in the Unity editor is an active operation that changes the editor's state — it triggers a scene load/switch which can cause unsaved changes to be lost and affects the current working environment. It goes beyond a simple read, as it manipulates the Unity Editor programmatically. Severity is medium because it can disrupt the current working session and potentially cause loss of unsaved work.
From the tool's definition Open a specified scene in the Unity editor
Documented attack patterns abuse exactly the kind of access open_scene gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Unity MCP with Ollama Integration, and nothing reaches the server without passing your rules. This is the rule we recommend for open_scene:
{
"version": "1",
"default": "deny",
"tools": {
"open_scene": {
"limits": [
{
"counter": "open_scene_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}open_scene 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.
Open a specified scene in the Unity editor. It is categorised as a Execute tool in the Unity MCP with Ollama Integration MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Unity MCP with Ollama Integration MCP server in PolicyLayer and add a rule for open_scene: 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 with Ollama Integration. Nothing to install.
open_scene 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 open_scene 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 open_scene. 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.
open_scene is provided by the Unity MCP with Ollama Integration MCP server (zundamonnovrchatkaisetu/unity-mcp-ollama). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Unity MCP with Ollama Integration, 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.
37 Unity MCP with Ollama Integration tools catalogued and risk-classified — across an index of 43,000+ MCP servers.