vibe_preview_status

List active vibe-preview sessions: project, profile, FPS, mode, frame count, error count.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 00 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-status.md

WHAT IT DOES

What vibe_preview_status does on Yaver

AI agents call vibe_preview_status 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.

RISK

Why vibe_preview_status is rated Low

This tool retrieves and queries the status of active preview sessions without side effects. It is a monitoring/observability tool that returns session metadata for inspection purposes only. No data is created, modified, deleted, or externally executed.

From the tool's definition Tool name and description indicate 'List active vibe-preview sessions' with read-only outputs: project, profile, FPS, mode, frame count, error count. No mention of creation, modification, deletion, or execution of external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

vibe_preview_status Allowed

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

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

FAQ

Questions about vibe_preview_status

What does the vibe_preview_status tool do? +

List active vibe-preview sessions: project, profile, FPS, mode, frame count, error count. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on vibe_preview_status? +

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

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

Can I rate-limit vibe_preview_status? +

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

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

vibe_preview_status 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

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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