testkit_run

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 60 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/testkit-run.md

WHAT IT DOES

What testkit_run does on Yaver

AI agents invoke testkit_run 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
`only`	string	—	Only run a single spec by name
`root`	string	—	Spec root (default: yaver-tests)
`video`	boolean	—	Force screencast capture for every spec (overrides per-spec artifacts.video). Frames flush to the run's artifact dir on both pass + fail so the workspace clip p
`headful`	boolean	—	Show the browser visibly
`retries`	integer	—	Flake retries (default 0)
`concurrency`	integer	—	Parallel workers (default 1)

Parameters from the server's own tool schema.

RISK

Why testkit_run is rated High

This tool executes arbitrary test suites against the developer's machine using a browser automation engine (chromedp). While not destructive by itself, it triggers external operations (browser automation, test execution) whose outcomes depend on test arguments and the state of the machine.

From the tool's definition Tool runs end-to-end test specs via embedded chromedp runner with side effects (browser automation, test execution) that depend on test arguments and environment state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs testkit_run 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_run, this is the rule to start with:

testkit_run Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "testkit_run": {
      "limits": [
        {
          "counter": "testkit_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every testkit_run call is checked against it from then on.

FAQ

Questions about testkit_run

What does the testkit_run tool do? +

Run the yaver-test-sdk specs end-to-end on the dev's machine via the embedded chromedp runner. Returns suite results inline. Use this to drive a 'fix → test → fix' loop without spawning Playwright. 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 testkit_run accept? +

testkit_run accepts 6 parameters: only, root, video, headful, retries, concurrency. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on testkit_run? +

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

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

Can I rate-limit testkit_run? +

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

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

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

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools → High-risk tools on this server →

Across the catalogue

shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →