editor_connect_signal
Connect a signal between nodes in the editor.
This record as markdown: /tools/yanhuifair-godot-mcp/editor-connect-signal.md
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
node | string | Yes | |
method | string | Yes | |
signal | string | Yes | |
target | object | — |
Parameters from the server's own tool schema.
Why editor_connect_signal is rated Medium
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
The rule that runs editor_connect_signal safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For editor_connect_signal, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every editor_connect_signal call is checked against it from then on.
Questions about editor_connect_signal
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.
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.
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.
editor_connect_signal 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 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.
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.
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.
More on Godot, and thousands of servers like it.
This server
Across the catalogue