unity_amplify_move_node
Move a node to a new position in the Amplify Shader Editor graph.
This record as markdown: /tools/anklebreaker-studio-unity-mcp-server/unity-amplify-move-node.md
What unity_amplify_move_node does on Unity MCP Server
AI agents use unity_amplify_move_node 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.
Why unity_amplify_move_node is rated Medium
This tool creates or modifies data (node position) in a reversible manner. The user can move a node to a different position and undo or reposition it again. It does not execute external operations, delete data, or create financial obligations. The blast radius is low since repositioning a shader node in the editor has minimal side effects and can be easily corrected. Classified as Write with low severity.
From the tool's definition Tool description states it 'Move[s] a node to a new position in the Amplify Shader Editor graph.' Moving a node in a shader editor modifies the visual/organizational state of the graph but does not delete data, execute arbitrary code, or cause irreversible…
Attacks that exploit this kind of access
The rule that runs unity_amplify_move_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_move_node, this is the rule to start with:
unity_amplify_move_node 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Unity MCP Server, apply this rule, and every unity_amplify_move_node call is checked against it from then on.
Questions about unity_amplify_move_node
Move a node to a new position in the Amplify Shader Editor graph. 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_move_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_move_node 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_move_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_move_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_move_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.
This server
Across the catalogue