runtime_peer_stop
Terminate a headless peer started by runtime_spawn_peers, or every one with all:true. DESTRUCTIVE (kills a child process). Stopping an already-stopped peer is a no-op, so this is safe to repeat; peers are also killed automatically when the server shuts down.
This record as markdown: /tools/breakpoint-mcp/runtime-peer-stop.md
What runtime_peer_stop does on Breakpoint
AI agents invoke runtime_peer_stop 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 |
|---|---|---|---|
id | string | — | Peer id to stop (from runtime_spawn_peers) — omit when using all |
all | boolean | — | Stop every peer this server spawned (default false) |
confirm | boolean | — | Skip the confirmation prompt (auto-approve) |
Parameters from the server's own tool schema.
Why runtime_peer_stop is rated High
runtime_peer_stop triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs runtime_peer_stop 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_peer_stop, this is the rule to start with:
runtime_peer_stop 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_peer_stop call is checked against it from then on.
Questions about runtime_peer_stop
Terminate a headless peer started by runtime_spawn_peers, or every one with all:true. DESTRUCTIVE (kills a child process). Stopping an already-stopped peer is a no-op, so this is safe to repeat; peers are also killed automatically when the server shuts down. 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_peer_stop accepts 3 parameters: id, all, confirm. 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_peer_stop: 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_peer_stop 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_peer_stop 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_peer_stop. 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_peer_stop 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