New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

yaver_verify_task

Run this task project's configured yaver-tests browser acceptance specs through Yaver's Playwright lane and return independently collected pass/fail evidence. Use after a user-visible browser change, before yaver_report_complete. A failed result is not completion: inspect the named feature/artifa...

SERVERYaver SOURCEyaver-cli
High RISK CLASS
Category Execute
Parameters 80 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/yaver-verify-task.md

What yaver_verify_task does on Yaver

AI agents invoke yaver_verify_task 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.

ParameterTypeRequiredDescription
trace boolean — Capture a Playwright trace. Defaults true.
video boolean — Record verification video and attach it to the task. Defaults true.
feature string — Optional exact Feature name from yaver-tests; empty runs every discovered browser feature.
profile string — Optional configured local Playwright profile name. Profile contents never leave the machine.
project string — Optional non-secret label for the report.
wait_url string — Optional readiness URL for dev_command.
dev_command string — Optional project-local command that starts the dev server for this run.
timeout_sec integer — Wall-clock deadline. Default 600 seconds.

Parameters from the server's own tool schema.

Why yaver_verify_task is rated High

Executes Playwright browser tests externally; results depend on current code state.

From the tool's definition Run...browser acceptance specs through Yaver's Playwright lane

Questions about yaver_verify_task

What does the yaver_verify_task tool do? +

Run this task project's configured yaver-tests browser acceptance specs through Yaver's Playwright lane and return independently collected pass/fail evidence. Use after a user-visible browser change, before yaver_report_complete. A failed result is not completion: inspect the named feature/artifacts, fix the code, and retry. The daemon binds the run to the current task project; no directory or secret environment can be supplied. Requires YAVER_TASK_ID. 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.

What parameters does yaver_verify_task accept? +

yaver_verify_task accepts 8 parameters: trace, video, feature, profile, project, wait_url, dev_command, timeout_sec. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on yaver_verify_task? +

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

yaver_verify_task is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit yaver_verify_task? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Yaver's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.