release_rollout

Set the rollout percentage for a release channel (0..100).

SERVERYaver SOURCEyaver-cli

Medium RISK CLASS

Category Write

Parameters 22 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/release-rollout.md

WHAT IT DOES

What release_rollout does on Yaver

AI agents use release_rollout to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.

Parameter	Type	Required	Description
`channel`	string	Yes
`percent`	integer	Yes

Parameters from the server's own tool schema.

RISK

Why release_rollout is rated Medium

This tool modifies the rollout configuration of a release channel, which is a reversible write operation (the percentage can be changed back). However, it has a high blast radius because changing rollout percentages directly affects what software version is served to end users — setting it incorrectly could expose all users to a broken release or cut off a good one.

From the tool's definition Set the rollout percentage for a release channel (0..100)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs release_rollout 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 release_rollout, this is the rule to start with:

release_rollout Rate-limited

release_rollout stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "release_rollout": {
      "limits": [
        {
          "counter": "release_rollout_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every release_rollout call is checked against it from then on.

FAQ

Questions about release_rollout

What does the release_rollout tool do? +

Set the rollout percentage for a release channel (0..100). It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does release_rollout accept? +

release_rollout accepts 2 parameters: channel, percent. Required: channel, percent. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on release_rollout? +

Register the Yaver MCP server in PolicyLayer and add a rule for release_rollout: 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 release_rollout? +

release_rollout is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit release_rollout? +

Yes. Add a rate_limit block to the release_rollout 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 release_rollout completely? +

Set action: deny in the PolicyLayer policy for release_rollout. 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 release_rollout? +

release_rollout 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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →