unity_amplify_status
Check if Amplify Shader Editor is installed in the project. Returns available commands, shader count, and function count. Only works when Amplify Shader Editor is imported.
This record as markdown: /tools/anklebreaker-studio-unity-mcp-server/unity-amplify-status.md
What unity_amplify_status does on Unity MCP Server
AI agents call unity_amplify_status 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_amplify_status is rated Low
This tool performs a read-only status check of the Amplify Shader Editor state within a Unity project. It queries and returns metadata (installation status, counts, available commands) without any side effects. No data is created, modified, deleted, or executed. This is a straightforward information retrieval operation with minimal security risk.
From the tool's definition Tool description states it 'Check[s] if Amplify Shader Editor is installed' and 'Returns available commands, shader count, and function count.' The verbs 'check' and 'returns' indicate pure information retrieval with no modification, creation, deletion, or…
Attacks that exploit this kind of access
The rule that runs unity_amplify_status 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_amplify_status, this is the rule to start with:
unity_amplify_status 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_amplify_status call is checked against it from then on.
Questions about unity_amplify_status
Check if Amplify Shader Editor is installed in the project. Returns available commands, shader count, and function count. Only works when Amplify Shader Editor is imported. 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_amplify_status: 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_amplify_status 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_amplify_status 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_amplify_status. 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_amplify_status 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