signal_disconnect
Disconnect a source node's signal from a target node's method (undoable). No-op if not connected.
This record as markdown: /tools/breakpoint-mcp/signal-disconnect.md
What signal_disconnect does on Breakpoint
AI agents use signal_disconnect to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Source node path (emitter) |
method | string | Yes | Connected method on the target |
signal | string | Yes | Signal name on the source |
target_path | string | Yes | Target node path (receiver) |
Parameters from the server's own tool schema.
Why signal_disconnect is rated Medium
This tool modifies state by removing a signal-slot connection, which is a reversible operation. The '(undoable)' qualifier confirms it is not destructive. While it affects system behavior, it does not execute arbitrary code or external operations, making it Write rather than Execute.
From the tool's definition Tool name 'signal_disconnect' and description states it disconnects a signal from a method, with explicit note that it is '(undoable)' indicating reversible modification.
Risk signalsAccepts file system path (path)
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 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 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 Breakpoint, apply this rule, and every signal_disconnect call is checked against it from then on.
Questions about signal_disconnect
Disconnect a source node's signal from a target node's method (undoable). No-op if not connected. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
signal_disconnect accepts 4 parameters: path, method, signal, target_path. Required: path, method, signal, target_path. The full parameter table on this page comes from the server's own tool schema.
Register the 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 Breakpoint. 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 Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue