vibe_preview_summaries

Read recent text summaries for a project (Phase 4). Each entry is a one-sentence description of what visibly changed between two frames, with before/after hashes. Default returns last 50; use limit to widen.

Server Yaver yaver-cli
Category Read
Risk class Low
Parameters 21 required

What vibe_preview_summaries does on Yaver

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

ParameterTypeRequiredDescription
limit integer Max entries (default 50, cap 500)
project string Yes Project name

Parameters from the server's own tool schema.

Why vibe_preview_summaries needs a policy

Even though vibe_preview_summaries only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about vibe_preview_summaries

What does the vibe_preview_summaries tool do? +

Read recent text summaries for a project (Phase 4). Each entry is a one-sentence description of what visibly changed between two frames, with before/after hashes. Default returns last 50; use limit to widen. 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_summaries accept? +

vibe_preview_summaries accepts 2 parameters: limit, 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_summaries? +

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

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

Can I rate-limit vibe_preview_summaries? +

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

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

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.