Start the game in play mode within the Unity editor.
AI agents invoke play 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.
This tool executes the game which runs arbitrary code (player scripts, physics systems, etc.). While not destructive or financial, it triggers external operations whose effects depend on game implementation and cannot be fully predicted without inspecting the game code.
From the tool's definition Tool name 'play' with description 'Start the game in play mode within the Unity editor' indicates execution of the game runtime environment and triggering of all associated game code, scripts, and systems.
Documented attack patterns abuse exactly the kind of access play 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 play:
{
"version": "1",
"default": "deny",
"tools": {
"play": {
"limits": [
{
"counter": "play_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}play 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.
Start the game in play mode within 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 play: 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.
play 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 play 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 play. 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.
play 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.