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...
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
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
Attacks that exploit this kind of access
The rule that runs yaver_verify_task 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 yaver_verify_task, this is the rule to start with:
yaver_verify_task 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 yaver_verify_task call is checked against it from then on.
Questions about 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/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.
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.
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.
yaver_verify_task 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 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.
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.
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.
Across the catalogue