Close the Amplify Shader Editor window. By default saves the graph before closing to prevent save dialogs.
AI agents use unity_amplify_close to create or update resources in Unity MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unity MCP Server environment.
This tool closes a UI window and saves the shader graph before doing so. The save operation writes data (persists the graph state), making it a Write action. It is reversible as the file can be re-edited. Severity is low since it only affects a shader editor window and saves the current graph state.
From the tool's definition Close the Amplify Shader Editor window. By default saves the graph before closing to prevent save dialogs.
Documented attack patterns abuse exactly the kind of access unity_amplify_close 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_amplify_close:
{
"version": "1",
"default": "deny",
"tools": {
"unity_amplify_close": {
"limits": [
{
"counter": "unity_amplify_close_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}unity_amplify_close stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Close the Amplify Shader Editor window. By default saves the graph before closing to prevent save dialogs. It is categorised as a Write tool in the Unity MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Unity MCP Server MCP server in PolicyLayer and add a rule for unity_amplify_close: 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_close is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the unity_amplify_close 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_close. 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_close 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.
Deterministic rules across all 324 Unity MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
324 Unity MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.