vibe_preview_clip_record
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.
This record as markdown: /tools/io-github-kivanccakmak-yaver/vibe-preview-clip-record.md
What vibe_preview_clip_record does on Yaver
AI agents invoke vibe_preview_clip_record to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| 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.
Why vibe_preview_clip_record is rated High
This tool executes external system commands (xcrun simctl, adb screenrecord) on simulators/emulators and drives the running app via Maestro automation. It triggers external operations whose effects depend on arguments — recording device screen sessions, interacting with running processes, and writing MP4 files.
From the tool's definition 'Record a short MP4 demo clip from a booted simulator/emulator while the running app is exercised by Maestro'; 'sim-ios uses xcrun simctl, sim-android uses adb screenrecord'
Attacks that exploit this kind of access
The rule that runs vibe_preview_clip_record 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_clip_record, this is the rule to start with:
vibe_preview_clip_record stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_clip_record call is checked against it from then on.
Questions about vibe_preview_clip_record
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 Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
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 Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
More on Yaver, and thousands of servers like it.
Across the catalogue