signal_disconnect

Disconnect a source node

SERVERGodot Breakpoint SOURCEjlivingston-Cipher/godot-breakpoint-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/godot-breakpoint-mcp/signal-disconnect.md

WHAT IT DOES

What signal_disconnect does on Godot Breakpoint

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

RISK

Why signal_disconnect is rated Medium

Disconnecting a signal removes a previously established connection between nodes, which is a reversible modification (the signal can be reconnected). This is a Write operation as it modifies the scene/node graph state. Description is sparse, lowering confidence slightly.

From the tool's definition 'Disconnect a source node' — disconnects a signal connection between nodes in Godot

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs signal_disconnect safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Godot Breakpoint, 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 Rate-limited

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.

View as policy code

policy.json

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

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Godot Breakpoint, apply this rule, and every signal_disconnect call is checked against it from then on.

FAQ

Questions about signal_disconnect

What does the signal_disconnect tool do? +

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

How do I enforce a policy on signal_disconnect? +

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

What risk level is signal_disconnect? +

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

Can I rate-limit signal_disconnect? +

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.

How do I block signal_disconnect completely? +

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.

What MCP server provides signal_disconnect? +

signal_disconnect is provided by the Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Godot Breakpoint, and thousands of servers like it.

This server

All 239 Godot Breakpoint tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →