unity_profiler_frame_data
Get CPU profiler frame data as a hierarchical timing breakdown. Shows function names, total/self time, call counts, and GC allocations. The profiler must be enabled and have captured at least one frame.
This record as markdown: /tools/anklebreaker-studio-unity-mcp-server/unity-profiler-frame-data.md
What unity_profiler_frame_data does on Unity MCP Server
AI agents call unity_profiler_frame_data 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_profiler_frame_data is rated Low
This tool retrieves and queries profiler metrics from an already-captured frame. It performs no modifications, deletions, code execution, or external operations—it simply reads diagnostic data. The requirement that 'the profiler must be enabled and have captured at least one frame' confirms it operates on existing data. This is a straightforward Read operation with minimal blast radius.
From the tool's definition Tool description states it 'Get[s] CPU profiler frame data' and 'Shows function names, total/self time, call counts, and GC allocations.' The verb 'Get' and the purely informational nature of profiling metrics (timing breakdowns, counts, allocations) indicate…
Attacks that exploit this kind of access
The rule that runs unity_profiler_frame_data 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_profiler_frame_data, this is the rule to start with:
unity_profiler_frame_data 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_profiler_frame_data call is checked against it from then on.
Questions about unity_profiler_frame_data
Get CPU profiler frame data as a hierarchical timing breakdown. Shows function names, total/self time, call counts, and GC allocations. The profiler must be enabled and have captured at least one frame. 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_profiler_frame_data: 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_profiler_frame_data 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_profiler_frame_data 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_profiler_frame_data. 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_profiler_frame_data 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