editor_connect_signal · Godot MCP: Risk & Policy

WHAT IT DOES

What editor_connect_signal does on Godot

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

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why editor_connect_signal needs a policy

This tool creates or modifies signal connections between nodes in the Godot editor, which is a reversible Write operation. Signal connections can be disconnected or reconfigured, so it is not Destructive. It does not execute arbitrary code or trigger external operations (Execute), nor does it directly delete data (Destructive).

From the tool's definition Tool name 'editor_connect_signal' and description 'Connect a signal between nodes in the editor' indicates modification of editor state and node signal connections.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

editor_connect_signal Rate-limited

editor_connect_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_connect_signal": {
      "limits": [
        {
          "counter": "editor_connect_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_connect_signal

What does the editor_connect_signal tool do? +

Connect a signal between nodes in the editor. 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_connect_signal accept? +

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

How do I enforce a policy on editor_connect_signal? +

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

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

Can I rate-limit editor_connect_signal? +

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

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

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