unity_memory_breakdown
Get detailed memory breakdown by asset type: textures, meshes, materials, shaders, audio clips, animation clips, fonts, render textures, and scriptable objects. Shows count, total size, and optionally top assets per category. Works without the Memory Profiler package (uses built-in Profiler APIs).
This record as markdown: /tools/anklebreaker-studio-unity-mcp-server/unity-memory-breakdown.md
What unity_memory_breakdown does on Unity MCP Server
AI agents call unity_memory_breakdown 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_memory_breakdown is rated Low
This tool performs read-only analysis of runtime memory allocation by asset type. It uses introspection APIs (Profiler) to gather diagnostic information without side effects. The tool does not execute code, modify assets, delete data, or trigger builds/operations. This is a straightforward diagnostic/telemetry operation classified as Read.
From the tool's definition Tool queries and retrieves memory profiling data ('Get detailed memory breakdown', 'Shows count, total size') using built-in Profiler APIs. No creation, modification, deletion, or execution of external operations occurs.
Attacks that exploit this kind of access
The rule that runs unity_memory_breakdown 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_memory_breakdown, this is the rule to start with:
unity_memory_breakdown 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_memory_breakdown call is checked against it from then on.
Questions about unity_memory_breakdown
Get detailed memory breakdown by asset type: textures, meshes, materials, shaders, audio clips, animation clips, fonts, render textures, and scriptable objects. Shows count, total size, and optionally top assets per category. Works without the Memory Profiler package (uses built-in Profiler APIs). 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_memory_breakdown: 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_memory_breakdown 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_memory_breakdown 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_memory_breakdown. 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_memory_breakdown 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