runtime_emit_signal

SERVERBreakpoint SOURCEbreakpoint-mcp

Medium RISK CLASS

Category Write

Parameters 52 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What runtime_emit_signal does on Breakpoint

AI agents use runtime_emit_signal 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
`args`	array	—
`path`	string	Yes
`peer`	string	—	Headless peer id from runtime_spawn_peers; omit for the default running game.
`signal`	string	Yes
`confirm`	boolean	—	Skip the confirmation prompt (auto-approve)

Parameters from the server's own tool schema.

RISK

Why runtime_emit_signal is rated Medium

An AI agent can call runtime_emit_signal 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 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 Rate-limited

runtime_emit_signal 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": {
    "runtime_emit_signal": {
      "limits": [
        {
          "counter": "runtime_emit_signal_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 runtime_emit_signal call is checked against it from then on.

FAQ

Questions about runtime_emit_signal

What does the runtime_emit_signal tool do? +

Emit a signal from a live node. DESTRUCTIVE — gated by confirmation. args must match the arity of the signal's CONNECTED callables, or the emission fails with emit_failed and no handler runs. Argument types are not checked, and a signal with no listeners always succeeds — so emitted:true does not mean a handler ran. 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 runtime_emit_signal accept? +

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.

How do I enforce a policy on runtime_emit_signal? +

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.

What risk level is runtime_emit_signal? +

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

Can I rate-limit runtime_emit_signal? +

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.

How do I block runtime_emit_signal completely? +

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.

What MCP server provides runtime_emit_signal? +

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.

KEEP EXPLORING

More on Breakpoint, and thousands of servers like it.

This server

All 280 Breakpoint tools →

Across the catalogue

emit_assumption_set on 0sec →team_manager_emit_decision on Team Manager MCP → The MCP Attack Database →

Guides

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