editor_disconnect_signal · Godot MCP: Risk & Policy

WHAT IT DOES

What editor_disconnect_signal does on Godot

AI agents use editor_disconnect_signal 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
`node`	string	Yes
`method`	object	—
`signal`	string	Yes
`target`	object	—

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why editor_disconnect_signal needs a policy

Disconnecting signals between nodes in Godot's scene tree is a write operation that modifies the project state (removes a signal binding) but remains reversible—the connection can be re-established. This is not destructive because signal disconnection does not permanently delete data or prevent undo.

From the tool's definition Tool is named 'editor_disconnect_signal' and described as 'Disconnect a signal between nodes.' Signal disconnection modifies the node graph structure by removing an existing connection, which is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

editor_disconnect_signal Rate-limited

editor_disconnect_signal 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": {
    "editor_disconnect_signal": {
      "limits": [
        {
          "counter": "editor_disconnect_signal_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 editor_disconnect_signal

What does the editor_disconnect_signal tool do? +

Disconnect a signal between nodes. 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 editor_disconnect_signal accept? +

editor_disconnect_signal accepts 4 parameters: node, method, signal, target. Required: node, signal. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on editor_disconnect_signal? +

Register the Godot MCP server in PolicyLayer and add a rule for editor_disconnect_signal: 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 editor_disconnect_signal? +

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

Can I rate-limit editor_disconnect_signal? +

Yes. Add a rate_limit block to the editor_disconnect_signal 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 editor_disconnect_signal completely? +

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

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