connect_signal
Connect a signal from one node to another node's method
This record as markdown: /tools/keeveeg-godot-mcp/connect-signal.md
What connect_signal does on Godot
AI agents use 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 |
|---|---|---|---|
method | string | Yes | Method to call on the target node |
signal | string | Yes | Signal name |
source | string | Yes | Node path emitting the signal |
target | string | Yes | Node path receiving the signal |
Parameters from the server's own tool schema.
Why connect_signal is rated Medium
This tool modifies the state of a Godot project by establishing new signal connections between nodes. While the connection itself is theoretically reversible (signals can be disconnected), it represents a persistent change to the project structure. This is Write-category behavior rather than Execute because it's configuration/data modification rather than code execution.
From the tool's definition Tool name 'connect_signal' and description 'Connect a signal from one node to another node's method' indicates modification of Godot scene graph signal connections, which creates new relationships between nodes.
Attacks that exploit this kind of access
The rule that runs 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 connect_signal, this is the rule to start with:
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 connect_signal call is checked against it from then on.
Questions about connect_signal
Connect a signal from one node to another node's method. 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.
connect_signal accepts 4 parameters: method, signal, source, target. Required: method, signal, source, target. 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 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.
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 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 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.
connect_signal is provided by the Godot MCP server (@keeveeg/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