This record as markdown: /tools/io-github-kivanccakmak-yaver/pytest-suite.md
What pytest_suite does on Yaver
AI agents invoke pytest_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 |
|---|---|---|---|
marker | string | — | Test marker filter |
verbose | boolean | — | |
coverage | boolean | — | |
directory | string | — |
Parameters from the server's own tool schema.
Why pytest_suite is rated High
pytest_suite executes arbitrary Python code via the pytest framework. While pytest is typically used for testing, it can execute any Python code including side effects (file creation, network calls, environment modifications, etc.). The execution context depends entirely on the test code being run, and a malicious agent could craft tests that perform harmful operations.
From the tool's definition 'Run Python tests with pytest' - the tool executes code (pytest) which runs arbitrary test scripts and their side effects.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs pytest_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 pytest_suite, this is the rule to start with:
pytest_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 pytest_suite call is checked against it from then on.
Questions about pytest_suite
Run Python tests with pytest. 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.
pytest_suite accepts 4 parameters: marker, verbose, coverage, 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 pytest_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.
pytest_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 pytest_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 pytest_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.
pytest_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