run_tests
Run the project's test suite. Auto-detects framework (go test, jest, vitest, pytest, cargo test, make test) or accepts a custom command.
This record as markdown: /tools/io-github-kivanccakmak-yaver/run-tests.md
What run_tests does on Yaver
AI agents invoke run_tests 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 |
|---|---|---|---|
command | string | — | Custom test command (auto-detected if empty) |
directory | string | — | Project directory (default: agent work dir) |
Parameters from the server's own tool schema.
Why run_tests is rated High
This tool executes code—either the project's test suite or custom commands provided by the user. While test execution itself is typically benign, the ability to specify custom commands elevates this to Execute rather than Read. An AI agent with misuse could run destructive or exfiltrative commands under the guise of testing.
From the tool's definition Tool description states it 'Run[s] the project's test suite' and can accept 'a custom command.' Running tests executes code in the project environment; accepting custom commands means arbitrary code execution is possible.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs run_tests 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 run_tests, this is the rule to start with:
run_tests 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 run_tests call is checked against it from then on.
Questions about run_tests
Run the project's test suite. Auto-detects framework (go test, jest, vitest, pytest, cargo test, make test) or accepts a custom command. 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.
run_tests accepts 2 parameters: command, directory. 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 run_tests: 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.
run_tests 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 run_tests 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 run_tests. 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.
run_tests 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