unity_debugger_event_details
Get detailed information about a specific Frame Debugger event: shader name, pass, keywords, vertex/index/instance counts, render target, batch break cause, and mesh info. The Frame Debugger must be enabled first.
This record as markdown: /tools/anklebreaker-studio-unity-mcp-server/unity-debugger-event-details.md
What unity_debugger_event_details does on Unity MCP Server
AI agents call unity_debugger_event_details to retrieve information from Unity MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why unity_debugger_event_details is rated Low
This tool queries and retrieves diagnostic/debugging information from an already-enabled Frame Debugger. It performs passive inspection of existing frame data without creating, modifying, deleting, or executing operations. The requirement that 'Frame Debugger must be enabled first' further confirms this is a read-only inspection tool.
From the tool's definition Tool retrieves detailed information about Frame Debugger events including shader name, pass, keywords, counts, render target, and mesh info.
Attacks that exploit this kind of access
The rule that runs unity_debugger_event_details safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unity MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unity_debugger_event_details, this is the rule to start with:
unity_debugger_event_details is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Unity MCP Server, apply this rule, and every unity_debugger_event_details call is checked against it from then on.
Questions about unity_debugger_event_details
Get detailed information about a specific Frame Debugger event: shader name, pass, keywords, vertex/index/instance counts, render target, batch break cause, and mesh info. The Frame Debugger must be enabled first. It is categorised as a Read tool in the Unity MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Unity MCP Server MCP server in PolicyLayer and add a rule for unity_debugger_event_details: 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_event_details is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the unity_debugger_event_details 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_event_details. 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_event_details 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.
More on Unity MCP Server, and thousands of servers like it.
This server
Across the catalogue