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 call runtime_peer_stop to permanently remove resources in Breakpoint, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| 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) |
Parameters from the server's own tool schema.
Why runtime_peer_stop is rated Critical
The tool explicitly terminates running processes. While stopping an already-stopped peer is a no-op, killing live processes is irreversible (the process state is lost). The 'all:true' option can terminate every spawned peer at once, giving it a high blast radius if misused.
From the tool's definition 'Terminate a headless peer', 'DESTRUCTIVE (kills a child process)', 'kills a child process'
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 is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
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 Destructive tool in the Breakpoint MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
runtime_peer_stop accepts 2 parameters: id, all. 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 Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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