Record a short MP4 demo clip from a booted simulator/emulator while the running app is exercised by Maestro (Phase 7). source: 'sim-ios' uses xcrun simctl, 'sim-android' uses adb screenrecord. Returns the clip metadata; poll vibe_preview_clips to see when status flips to ready.
AI agents call vibe_preview_clip_record 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
source | string | — | Capture source (auto-detect if omitted) |
project | string | Yes | Project name |
duration_max_sec | integer | — | Recording duration cap (default 12, max 30) |
Parameters from the server's own tool schema.
Even though vibe_preview_clip_record 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.
Attacks that exploit this kind of access
Record a short MP4 demo clip from a booted simulator/emulator while the running app is exercised by Maestro (Phase 7). source: 'sim-ios' uses xcrun simctl, 'sim-android' uses adb screenrecord. Returns the clip metadata; poll vibe_preview_clips to see when status flips to ready. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
vibe_preview_clip_record accepts 3 parameters: source, project, duration_max_sec. 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_clip_record: 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_clip_record 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_clip_record 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_clip_record. 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_clip_record 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.