vibe_preview_release

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What vibe_preview_release does on Yaver

AI agents call vibe_preview_release 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
`project`	string	Yes	Project name

Parameters from the server's own tool schema.

RISK

Why vibe_preview_release is rated Low

Queries preview session status without modifying state or executing operations.

From the tool's definition reports the still-active session and capture loop; checks blockers

Attacks that exploit this kind of access

RECOMMENDED RULE

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

vibe_preview_release Allowed

vibe_preview_release 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": {
    "vibe_preview_release": {}
  }
}

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 vibe_preview_release call is checked against it from then on.

FAQ

Questions about vibe_preview_release

What does the vibe_preview_release tool do? +

Answer 'could a new preview session for this project be claimed right now?' — reports the still-active session and any capture loop still winding down, with named blockers. Poll this after vibe_preview_stop instead of sleeping. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does vibe_preview_release accept? +

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

How do I enforce a policy on vibe_preview_release? +

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

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

Can I rate-limit vibe_preview_release? +

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

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

vibe_preview_release 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

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