unity_shadergraph_get_edges
Get all edges (connections) in a Shader Graph. Returns source and target node IDs with slot IDs, showing how nodes are wired together.
This record as markdown: /tools/anklebreaker-studio-unity-mcp-server/unity-shadergraph-get-edges.md
What unity_shadergraph_get_edges does on Unity MCP Server
AI agents call unity_shadergraph_get_edges 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_shadergraph_get_edges is rated Low
This tool queries and returns existing data about shader graph connections (edges between nodes). It performs no modifications, deletions, code execution, or side effects. The action is a straightforward data retrieval operation with no blast radius if misused by an agent — it cannot corrupt or change shader state, only read it.
From the tool's definition Tool name contains 'get' and description states 'Get all edges (connections)' and 'showing how nodes are wired together' — purely retrieves information about shader graph structure without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs unity_shadergraph_get_edges 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_shadergraph_get_edges, this is the rule to start with:
unity_shadergraph_get_edges 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_shadergraph_get_edges call is checked against it from then on.
Questions about unity_shadergraph_get_edges
Get all edges (connections) in a Shader Graph. Returns source and target node IDs with slot IDs, showing how nodes are wired together. 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_shadergraph_get_edges: 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_shadergraph_get_edges 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_shadergraph_get_edges 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_shadergraph_get_edges. 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_shadergraph_get_edges 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