AI agents invoke change_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.
In Unity, changing a scene switches the active editor/runtime scene, which triggers execution of scene lifecycle methods and can cause loss of unsaved changes in the current scene. Given sibling tools like 'execute_command', 'delete_object', and 'build', this server performs broad editor control.
From the tool's definition Tool name 'change_scene' on a server that 'controls the Unity Editor programmatically'; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access change_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 change_scene:
{
"version": "1",
"default": "deny",
"tools": {
"change_scene": {
"limits": [
{
"counter": "change_scene_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}change_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.
change_scene. 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 change_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.
change_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 change_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 change_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.
change_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.