New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

runtime_release_control

Release the control lease. Matching clientId is required unless force=true.

SERVERYaver SOURCEyaver-cli
High RISK CLASS
Category Execute
Parameters 32 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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

Questions about runtime_release_control

What does the runtime_release_control tool do? +

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.

What parameters does runtime_release_control accept? +

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.

How do I enforce a policy on runtime_release_control? +

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.

What risk level is runtime_release_control? +

runtime_release_control is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit runtime_release_control? +

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.

How do I block runtime_release_control completely? +

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.

What MCP server provides runtime_release_control? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Yaver's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.