This record as markdown: /tools/chanceflow-godot-mcp/signal-disconnect.md
What signal_disconnect does on Godot
AI agents use signal_disconnect 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.
Why signal_disconnect is rated Medium
Disconnecting a signal modifies the state of event listeners in the Godot engine without deleting them permanently. This is reversible (signals can be reconnected), so it fits Write rather than Destructive. The medium severity reflects that misuse could disrupt game logic or UI responsiveness, but the effects are containable and reversible.
From the tool's definition Tool name is `signal_disconnect`, which operates on Godot's signal system (a core event mechanism). The absence of a description limits confidence, but 'disconnect' indicates modification of signal bindings/connections rather than retrieval or deletion.
Attacks that exploit this kind of access
The rule that runs signal_disconnect 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 signal_disconnect, this is the rule to start with:
signal_disconnect 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 signal_disconnect call is checked against it from then on.
Questions about signal_disconnect
signal_disconnect is a write tool on the Godot MCP server. 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.
Register the Godot MCP server in PolicyLayer and add a rule for signal_disconnect: 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.
signal_disconnect 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 signal_disconnect 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 signal_disconnect. 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.
signal_disconnect is provided by the Godot MCP server (chanceflow/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