This record as markdown: /tools/io-github-kivanccakmak-yaver/go-test-suite.md
What go_test_suite does on Yaver
AI agents invoke go_test_suite 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 |
|---|---|---|---|
race | boolean | — | |
cover | boolean | — | |
verbose | boolean | — | |
directory | string | — |
Parameters from the server's own tool schema.
Why go_test_suite is rated High
This tool runs Go tests, which involves executing code in the environment. While tests are nominally read-only, they can have side effects depending on what the tests do (network calls, file I/O, database writes, etc.). The blast radius is high because arbitrary test code runs in the local dev environment, and a misconfigured or malicious test suite could cause significant harm.
From the tool's definition 'Run Go tests' — actively executes Go test suite code
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs go_test_suite 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 go_test_suite, this is the rule to start with:
go_test_suite 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 go_test_suite call is checked against it from then on.
Questions about go_test_suite
Run Go tests. 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.
go_test_suite accepts 4 parameters: race, cover, verbose, 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 go_test_suite: 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.
go_test_suite 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 go_test_suite 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 go_test_suite. 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.
go_test_suite 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