runtime_emit_signal
Emit a signal from a live node. DESTRUCTIVE — gated by confirmation.
This record as markdown: /tools/breakpoint-mcp/runtime-emit-signal.md
What runtime_emit_signal does on Breakpoint
AI agents invoke runtime_emit_signal to trigger actions in Breakpoint. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
args | array | — | |
path | string | Yes | |
peer | string | — | Target a headless peer by id (from runtime_spawn_peers). Omit to address the default running game. |
signal | string | Yes | |
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
Parameters from the server's own tool schema.
Why runtime_emit_signal is rated High
Emitting a signal from a live node triggers external operations and event handlers at runtime, whose effects depend on the signal and node arguments. The description labels it DESTRUCTIVE, but since it fires signals (which execute callbacks/side effects) rather than directly deleting/overwriting data, Execute is the most accurate category. The 'DESTRUCTIVE' label and runtime nature make severity high.
From the tool's definition 'Emit a signal from a live node. DESTRUCTIVE — gated by confirmation.'
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs runtime_emit_signal 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 runtime_emit_signal, this is the rule to start with:
runtime_emit_signal stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 runtime_emit_signal call is checked against it from then on.
Questions about runtime_emit_signal
Emit a signal from a live node. DESTRUCTIVE — gated by confirmation. It is categorised as a Execute tool in the Breakpoint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
runtime_emit_signal accepts 5 parameters: args, path, peer, signal, confirm. Required: path, signal. 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 runtime_emit_signal: 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.
runtime_emit_signal is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the runtime_emit_signal 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 runtime_emit_signal. 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.
runtime_emit_signal 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.
Across the catalogue