signal_connect
Connect a source node's signal to a target node's method (undoable). Persistent by default (flags=2, CONNECT_PERSIST) so it saves into the scene. No-op if already connected.
This record as markdown: /tools/breakpoint-mcp/signal-connect.md
What signal_connect does on Breakpoint
AI agents use signal_connect 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) |
flags | integer | — | Object.ConnectFlags bitmask (default 2 = CONNECT_PERSIST) |
method | string | Yes | Method to call 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_connect is rated Medium
This tool creates a new signal connection between nodes and persists it into the scene file. It modifies scene data reversibly (explicitly noted as undoable), making it a Write operation. Misuse could wire up unintended signal/method connections affecting scene behavior, but it is reversible.
From the tool's definition Connect a source node's signal to a target node's method (undoable). Persistent by default (flags=2, CONNECT_PERSIST) so it saves into the scene. No-op if already connected.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs signal_connect 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_connect, this is the rule to start with:
signal_connect 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_connect call is checked against it from then on.
Questions about signal_connect
Connect a source node's signal to a target node's method (undoable). Persistent by default (flags=2, CONNECT_PERSIST) so it saves into the scene. No-op if already 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_connect accepts 5 parameters: path, flags, 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_connect: 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_connect 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_connect 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_connect. 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_connect 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