signal_list_connections

List a node's outgoing signal connections (signal, target node path, method, flags). Optionally filter to one signal. Read-only.

SERVERBreakpoint SOURCEbreakpoint-mcp

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What signal_list_connections does on Breakpoint

AI agents call signal_list_connections to retrieve information from Breakpoint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`path`	string	Yes	Node path relative to the scene root
`signal`	string	—	Only list connections for this signal

Parameters from the server's own tool schema.

RISK

Why signal_list_connections is rated Low

Even though signal_list_connections only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsAccepts file system path (path)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs signal_list_connections 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_list_connections, this is the rule to start with:

signal_list_connections Allowed

signal_list_connections is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "signal_list_connections": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about signal_list_connections

What does the signal_list_connections tool do? +

List a node's outgoing signal connections (signal, target node path, method, flags). Optionally filter to one signal. Read-only. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.

What parameters does signal_list_connections accept? +

signal_list_connections accepts 2 parameters: path, signal. Required: path. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on signal_list_connections? +

Register the Breakpoint MCP server in PolicyLayer and add a rule for signal_list_connections: 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_list_connections? +

signal_list_connections is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit signal_list_connections? +

Yes. Add a rate_limit block to the signal_list_connections 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_list_connections completely? +

Set action: deny in the PolicyLayer policy for signal_list_connections. 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_list_connections? +

signal_list_connections 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

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →