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 |
|---|---|---|---|
flags | object | — | Connection flags |
signal | string | Yes | Signal name (e.g. "body_entered", "pressed") |
to_node | string | Yes | Target node path |
unbinds | object | — | Number of unbinds |
from_node | string | Yes | Source node path |
scene_path | string | Yes | Path to .tscn file |
method_name | string | Yes | Method name on target (e.g. "_on_body_entered") |
Parameters from the server's own tool schema.
This tool modifies the signal connection graph of a Godot project by establishing new connections between nodes. While reversible (signals can be disconnected), it alters application state and behavior in ways that could have cascading effects on game logic if misused by an AI agent.
From the tool's definition Tool name 'connect_signal' and description 'Connect a signal between nodes' indicates modification of node signal connections in Godot, which changes the runtime behavior and event flow of the game/application.
Attacks that exploit this kind of access
Connect 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.
connect_signal accepts 7 parameters: flags, signal, to_node, unbinds, from_node, scene_path, method_name. Required: signal, to_node, from_node, scene_path, method_name. 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 (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
connect_signal is one line of Godot's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →