testkit_self_heal_selector
Given a CSS selector that no longer matches and a DOM HTML snapshot, ask the user's vision/text LLM to propose a new selector. Returns the suggested replacement plus the model's reasoning. Used by the autonomous test-fix loop.
This record as markdown: /tools/io-github-kivanccakmak-yaver/testkit-self-heal-selector.md
What testkit_self_heal_selector does on Yaver
AI agents invoke testkit_self_heal_selector 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 |
|---|---|---|---|
intent | string | — | Optional: what the selector was supposed to find |
dom_html | string | Yes | The current page HTML |
failed_selector | string | Yes | The CSS selector that failed |
Parameters from the server's own tool schema.
Why testkit_self_heal_selector is rated High
This tool invokes an external LLM model to analyze a DOM snapshot and generate CSS selector replacements, which constitutes triggering an external operation. It is part of an autonomous test-fix loop, meaning its outputs may be automatically applied.
From the tool's definition 'ask the user's vision/text LLM to propose a new selector' and 'Used by the autonomous test-fix loop' — triggers an external LLM call and returns AI-generated selector replacements used in automated test fixing
Attacks that exploit this kind of access
The rule that runs testkit_self_heal_selector 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_self_heal_selector, this is the rule to start with:
testkit_self_heal_selector 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_self_heal_selector call is checked against it from then on.
Questions about testkit_self_heal_selector
Given a CSS selector that no longer matches and a DOM HTML snapshot, ask the user's vision/text LLM to propose a new selector. Returns the suggested replacement plus the model's reasoning. Used by the autonomous test-fix loop. 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_self_heal_selector accepts 3 parameters: intent, dom_html, failed_selector. Required: dom_html, failed_selector. 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_self_heal_selector: 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_self_heal_selector 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_self_heal_selector 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_self_heal_selector. 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_self_heal_selector 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