This record as markdown: /tools/yanhuifair-godot-mcp/disconnect-signal.md
What disconnect_signal does on Godot
AI agents use 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
signal | string | Yes | Signal name |
to_node | string | Yes | Target node path |
from_node | string | Yes | Source node path |
scene_path | string | Yes | Path to .tscn file |
method_name | string | Yes | Method name on target |
Parameters from the server's own tool schema.
Why disconnect_signal is rated Medium
Disconnecting a signal modifies the runtime behavior and signal routing of a Godot application by removing a callback connection. This is a reversible operation (signals can be reconnected) that changes application state, fitting the Write category.
From the tool's definition Tool name 'disconnect_signal' combined with description 'Disconnect a signal' indicates modification of signal connections in Godot, which alters the event-driven architecture of a game/application without irreversibly deleting core data.
Attacks that exploit this kind of access
The rule that runs disconnect_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 disconnect_signal, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every disconnect_signal call is checked against it from then on.
Questions about disconnect_signal
Disconnect a signal. 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.
disconnect_signal accepts 5 parameters: signal, to_node, 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 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.
disconnect_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 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.
Set action: deny in the PolicyLayer policy for 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.
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.
More on Godot, and thousands of servers like it.
This server
Across the catalogue