Enable or disable the Frame Debugger. When enabled, Unity pauses rendering after a specific draw call so you can inspect the GPU state. Uses reflection to access internal Unity APIs (Unity 6+).
AI agents invoke unity_debugger_enable 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.
This tool triggers an external operation (enabling/disabling Unity's Frame Debugger and pausing rendering) that affects the Unity Editor's runtime state. It uses reflection to access internal Unity APIs, which constitutes executing an engine-level operation. It doesn't read data passively, nor does it write/delete persistent data — it controls a debug execution mode.
From the tool's definition Enable or disable the Frame Debugger. When enabled, Unity pauses rendering after a specific draw call so you can inspect the GPU state. Uses reflection to access internal Unity APIs.
Documented attack patterns abuse exactly the kind of access unity_debugger_enable 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_debugger_enable:
{
"version": "1",
"default": "deny",
"tools": {
"unity_debugger_enable": {
"limits": [
{
"counter": "unity_debugger_enable_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} unity_debugger_enable 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.
Enable or disable the Frame Debugger. When enabled, Unity pauses rendering after a specific draw call so you can inspect the GPU state. Uses reflection to access internal Unity APIs (Unity 6+). 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_debugger_enable: 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_debugger_enable 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_debugger_enable 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_debugger_enable. 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_debugger_enable 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.
Start from Unity MCP Server, 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.
324 Unity MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.