This record as markdown: /tools/keeveeg-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 |
|---|---|---|---|
method | string | Yes | Method that was connected |
signal | string | Yes | Signal name |
source | string | Yes | Node path that emits the signal |
target | string | Yes | Node path that receives the signal |
Parameters from the server's own tool schema.
Why disconnect_signal is rated Medium
Disconnecting signals modifies the event system and application behavior by removing callback connections. While reversible and not destructive, it is a write operation that changes application state. Severity is medium because misuse could break application functionality but is not data-destructive or financial in nature.
From the tool's definition Tool name 'disconnect_signal' and description 'Disconnect a signal connection' indicate modification of signal bindings in Godot engine. This is a reversible change (connections can be re-established) that alters the state of the application.
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 connection. 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 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 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 (@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