release_list

List releases in a self-hosted OTA channel (default: production). Shows latest pointer, rollout percent, and every historical bundle.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/release-list.md

WHAT IT DOES

What release_list does on Yaver

AI agents call release_list to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`channel`	string	—	Channel name, default production

Parameters from the server's own tool schema.

RISK

Why release_list is rated Low

This tool queries and returns information about releases in an OTA (Over-The-Air) channel without creating, modifying, or deleting data. It is a read-only operation with minimal blast radius if misused—worst case would be information disclosure about deployment history.

From the tool's definition 'List releases' and 'Shows latest pointer, rollout percent, and every historical bundle' indicate data retrieval with no modifications or side effects.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

release_list Allowed

release_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "release_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about release_list

What does the release_list tool do? +

List releases in a self-hosted OTA channel (default: production). Shows latest pointer, rollout percent, and every historical bundle. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does release_list accept? +

release_list accepts 1 parameter: channel. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on release_list? +

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

release_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit release_list? +

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

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

release_list 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →