disconnect_shader_graph_nodes · Godot MCP: Risk & Policy

WHAT IT DOES

What disconnect_shader_graph_nodes does on Godot

AI agents use disconnect_shader_graph_nodes to create or update resources in Godot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.

PARAMETERS

Parameter	Type	Required	Description
`path`	string	Yes	Path to VisualShader .tres
`to_node`	number	Yes	Target node index
`to_port`	number	Yes	Target port index
`from_node`	number	Yes	Source node index
`from_port`	number	Yes	Source port index

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why disconnect_shader_graph_nodes needs a policy

Disconnecting shader graph nodes modifies the visual shader graph by removing a connection between two ports. This is a reversible write operation (the connection can be re-established), not a destructive one since no data is permanently deleted — only the link between nodes is removed.

From the tool's definition Disconnect two node ports in a VisualShader graph

Risk signalsAccepts file system path (path)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

disconnect_shader_graph_nodes Rate-limited

disconnect_shader_graph_nodes 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "disconnect_shader_graph_nodes": {
      "limits": [
        {
          "counter": "disconnect_shader_graph_nodes_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Godot, so you can run agents against it safely.

FAQ

Questions about disconnect_shader_graph_nodes

What does the disconnect_shader_graph_nodes tool do? +

Disconnect two node ports in a VisualShader graph. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does disconnect_shader_graph_nodes accept? +

disconnect_shader_graph_nodes accepts 5 parameters: path, to_node, to_port, from_node, from_port. Required: path, to_node, to_port, from_node, from_port. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on disconnect_shader_graph_nodes? +

Register the Godot MCP server in PolicyLayer and add a rule for disconnect_shader_graph_nodes: 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 Godot. Nothing to install.

What risk level is disconnect_shader_graph_nodes? +

disconnect_shader_graph_nodes is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit disconnect_shader_graph_nodes? +

Yes. Add a rate_limit block to the disconnect_shader_graph_nodes 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.

How do I block disconnect_shader_graph_nodes completely? +

Set action: deny in the PolicyLayer policy for disconnect_shader_graph_nodes. 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.

What MCP server provides disconnect_shader_graph_nodes? +

disconnect_shader_graph_nodes is provided by the Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.