vibe_preview_clips
List recent clips for a project, newest first. Each clip has id, source, status (recording|ready|failed), durationSec, sizeBytes.
This record as markdown: /tools/io-github-kivanccakmak-yaver/vibe-preview-clips.md
What vibe_preview_clips does on Yaver
AI agents call vibe_preview_clips 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.
Why vibe_preview_clips is rated Low
This tool retrieves and queries existing data about clips without modifying, deleting, or executing anything. It has minimal blast radius—an AI agent using it can only discover what clips exist and their properties. No financial, destructive, or code execution capabilities are present.
From the tool's definition Tool description states it "List[s] recent clips for a project" and returns metadata (id, source, status, durationSec, sizeBytes).
Attacks that exploit this kind of access
The rule that runs vibe_preview_clips 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_clips, this is the rule to start with:
vibe_preview_clips is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every vibe_preview_clips call is checked against it from then on.
Questions about vibe_preview_clips
List recent clips for a project, newest first. Each clip has id, source, status (recording|ready|failed), durationSec, sizeBytes. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
vibe_preview_clips accepts 1 parameter: project. Required: project. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for vibe_preview_clips: 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.
vibe_preview_clips is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the vibe_preview_clips 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.
Set action: deny in the PolicyLayer policy for vibe_preview_clips. 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.
vibe_preview_clips 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.
This server
Across the catalogue