runtime_stop
Delete a remote-runtime session (shuts down the local live state; the sim itself stays booted for reuse).
This record as markdown: /tools/io-github-kivanccakmak-yaver/runtime-stop.md
What runtime_stop does on Yaver
AI agents call runtime_stop to permanently remove resources in Yaver, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
sessionId | string | Yes |
Parameters from the server's own tool schema.
Why runtime_stop is rated Critical
Terminates a runtime session irreversibly, destroying live state that cannot be recovered.
From the tool's definition Delete a remote-runtime session; shuts down the local live state
Attacks that exploit this kind of access
The rule that runs runtime_stop safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For runtime_stop, this is the rule to start with:
runtime_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 Yaver, apply this rule, and every runtime_stop call is checked against it from then on.
Questions about runtime_stop
Delete a remote-runtime session (shuts down the local live state; the sim itself stays booted for reuse). It is categorised as a Destructive tool in the Yaver MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
runtime_stop accepts 1 parameter: sessionId. Required: sessionId. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for runtime_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 Yaver. Nothing to install.
runtime_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_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_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_stop is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
Across the catalogue