unity_amplify_remove_node
Remove a node from the currently open Amplify Shader Editor graph by its unique ID. Cannot remove the master/output node.
This record as markdown: /tools/anklebreaker-studio-unity-mcp-server/unity-amplify-remove-node.md
What unity_amplify_remove_node does on Unity MCP Server
AI agents call unity_amplify_remove_node to permanently remove resources in Unity MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why unity_amplify_remove_node is rated Critical
Removing a node from a shader graph destroys that node and its associated connections. While the master/output node is protected, removing intermediate nodes can break shader logic irreversibly (without an explicit undo). This qualifies as Destructive. Severity is medium because it affects a shader graph element within a single project rather than system-wide data.
From the tool's definition 'Remove a node from the currently open Amplify Shader Editor graph' — removing a node is an irreversible deletion of that node and its connections from the shader graph.
Attacks that exploit this kind of access
The rule that runs unity_amplify_remove_node 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_remove_node, this is the rule to start with:
unity_amplify_remove_node is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Unity MCP Server, apply this rule, and every unity_amplify_remove_node call is checked against it from then on.
Questions about unity_amplify_remove_node
Remove a node from the currently open Amplify Shader Editor graph by its unique ID. Cannot remove the master/output node. It is categorised as a Destructive tool in the Unity MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Unity MCP Server MCP server in PolicyLayer and add a rule for unity_amplify_remove_node: 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_remove_node is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the unity_amplify_remove_node 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_remove_node. 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_remove_node 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.
Across the catalogue