signal_list
List the signals a node declares (name and argument names), including user signals. Read-only.
This record as markdown: /tools/breakpoint-mcp/signal-list.md
What signal_list does on Breakpoint
AI agents call signal_list 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 |
Parameters from the server's own tool schema.
Why signal_list is rated Low
This tool retrieves metadata about signals without modifying any state, triggering external effects, or exposing sensitive financial operations. The explicit 'Read-only' designation and list operation confirm it belongs in the Read category with low severity, as misuse would only expose information about available signals.
From the tool's definition Tool is explicitly described as 'Read-only' and performs a listing operation (signal_list) to retrieve signal declarations from a node.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs signal_list 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, this is the rule to start with:
signal_list is read-only, so it stays allowed. 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_list call is checked against it from then on.
Questions about signal_list
List the signals a node declares (name and argument names), including user signals. Read-only. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
signal_list accepts 1 parameter: path. Required: 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_list: 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_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the signal_list 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_list. 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_list 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