testkit_visual_check
Run the QA vision inspector on a Selenium session (or an image) and return PASS/WARN/FAIL + issues. The visual-assertion step for automated browser tests: start → navigate → snapshot (DOM/accessibility) → testkit_visual_check (pixel judgment). Requires a vision provider (MISTRAL/OPENAI/ANTHROPIC ...
This record as markdown: /tools/io-github-kivanccakmak-yaver/testkit-visual-check.md
What testkit_visual_check does on Yaver
AI agents invoke testkit_visual_check 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 |
|---|---|---|---|
image | string | — | Alternative to session_id: path / base64: / data: / URL. |
model | string | — | |
provider | string | — | |
question | string | — | Test-specific visual question. Defaults to a regression prompt. |
session_id | string | — | Selenium session id to screenshot and judge. |
Parameters from the server's own tool schema.
Why testkit_visual_check is rated High
Executes a visual inspection process against a live browser session, triggering external operations.
From the tool's definition Run the QA vision inspector on a Selenium session
Attacks that exploit this kind of access
The rule that runs testkit_visual_check 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 testkit_visual_check, this is the rule to start with:
testkit_visual_check 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 testkit_visual_check call is checked against it from then on.
Questions about testkit_visual_check
Run the QA vision inspector on a Selenium session (or an image) and return PASS/WARN/FAIL + issues. The visual-assertion step for automated browser tests: start → navigate → snapshot (DOM/accessibility) → testkit_visual_check (pixel judgment). Requires a vision provider (MISTRAL/OPENAI/ANTHROPIC key) or an explicit provider/model. 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.
testkit_visual_check accepts 5 parameters: image, model, provider, question, session_id. 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 testkit_visual_check: 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.
testkit_visual_check 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 testkit_visual_check 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 testkit_visual_check. 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.
testkit_visual_check 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