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.

SERVERBreakpoint SOURCEbreakpoint-mcp

Medium RISK CLASS

Category Write

Parameters 54 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

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.

RISK

Why signal_connect is rated Medium

An AI agent can call signal_connect faster than any human can review: one bad instruction and it creates or modifies resources in Breakpoint by the hundred, each call as confident as the last.

Risk signalsAccepts file system path (path)

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "signal_connect": {
      "limits": [
        {
          "counter": "signal_connect_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 Breakpoint, apply this rule, and every signal_connect call is checked against it from then on.

FAQ

Questions about signal_connect

What does the signal_connect tool do? +

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.

What parameters does signal_connect accept? +

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.

How do I enforce a policy on signal_connect? +

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.

What risk level is signal_connect? +

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

Can I rate-limit signal_connect? +

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.

How do I block signal_connect completely? +

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.

What MCP server provides signal_connect? +

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.

KEEP EXPLORING

More on Breakpoint, and thousands of servers like it.

This server

All 280 Breakpoint tools →

Across the catalogue

connect-gmail on Meme MCP Server → The MCP Attack Database →

Guides

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