testkit_flake_report
Per-spec failure ratios over the last 100 runs. Use to identify chronically broken or flaky specs that need attention.
This record as markdown: /tools/io-github-kivanccakmak-yaver/testkit-flake-report.md
What testkit_flake_report does on Yaver
AI agents call testkit_flake_report to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
root | string | — | Spec root (default: yaver-tests) |
Parameters from the server's own tool schema.
Why testkit_flake_report is rated Low
This tool queries test metrics and reporting data without side effects. It is purely informational, allowing users to analyze flakiness patterns. No data is modified, deleted, or executed. The read-only nature and diagnostic purpose place it in the Read category with low severity—misuse would only expose test data, not affect system state or operations.
From the tool's definition Tool retrieves historical test failure data ('failure ratios over the last 100 runs') with no indication of modifying, deleting, or executing system operations. Description uses passive language ('use to identify') indicating data inspection only.
Attacks that exploit this kind of access
The rule that runs testkit_flake_report 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_flake_report, this is the rule to start with:
testkit_flake_report is read-only, so it stays allowed. 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_flake_report call is checked against it from then on.
Questions about testkit_flake_report
Per-spec failure ratios over the last 100 runs. Use to identify chronically broken or flaky specs that need attention. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
testkit_flake_report accepts 1 parameter: root. 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_flake_report: 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_flake_report is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the testkit_flake_report 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_flake_report. 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_flake_report 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.
This server
Across the catalogue