disconnect_signal · Godot MCP Server MCP: Risk & Policy

WHAT IT DOES

What disconnect_signal does on Godot MCP Server

AI agents use disconnect_signal to create or update resources in Godot MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot MCP Server environment.

WHY IT NEEDS A POLICY

Why disconnect_signal needs a policy

Disconnecting a signal is a modification operation that changes the state of the Godot scene graph (removes a connection between nodes), but it is reversible (the signal can be reconnected). This is less severe than Execute (which would run arbitrary code) and far less severe than Destructive (which would permanently delete data).

From the tool's definition Tool name is 'disconnect_signal' and description states it 'Disconnect a previously connected signal' — this modifies the state of signal connections in Godot scenes, which is a reversible structural change to the game project.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

disconnect_signal Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "disconnect_signal": {
      "limits": [
        {
          "counter": "disconnect_signal_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Godot MCP Server, so you can run agents against it safely.

FAQ

Questions about disconnect_signal

What does the disconnect_signal tool do? +

Disconnect a previously connected signal. It is categorised as a Write tool in the Godot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on disconnect_signal? +

Register the Godot MCP Server 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 MCP Server. Nothing to install.

What risk level is disconnect_signal? +

disconnect_signal is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit disconnect_signal? +

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.

How do I block disconnect_signal completely? +

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.

What MCP server provides disconnect_signal? +

disconnect_signal is provided by the Godot MCP Server MCP server (neondeex/godotmcp-pro-free-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.