runtime_release_control
Release the control lease. Matching clientId is required unless force=true.
This record as markdown: /tools/io-github-kivanccakmak-yaver/runtime-release-control.md
What runtime_release_control does on Yaver
AI agents invoke runtime_release_control to trigger actions in Yaver. 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 |
|---|---|---|---|
force | boolean | — | |
clientId | string | Yes | |
sessionId | string | Yes |
Parameters from the server's own tool schema.
Why runtime_release_control is rated High
Releasing a control lease triggers an operational state change affecting runtime control flow.
From the tool's definition Release the control lease... unless force=true
Attacks that exploit this kind of access
The rule that runs runtime_release_control 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_release_control, this is the rule to start with:
runtime_release_control 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 Yaver, apply this rule, and every runtime_release_control call is checked against it from then on.
Questions about runtime_release_control
Release the control lease. Matching clientId is required unless force=true. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
runtime_release_control accepts 3 parameters: force, clientId, sessionId. Required: clientId, 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_release_control: 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_release_control 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_release_control 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_release_control. 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_release_control 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