Runs pytest and returns structured test results (passed, failed, errors, skipped, failures).
AI agents invoke pytest to trigger actions in Lint. 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.
The tool explicitly runs pytest, which executes test code on the system. Running arbitrary test suites can execute code with side effects, access files, network resources, or other system resources depending on what the tests do. This is clearly an Execute category action with medium severity as it's scoped to test execution but could have broad effects depending on the test suite.
From the tool's definition Runs pytest and returns structured test results
Documented attack patterns abuse exactly the kind of access pytest gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Lint, and nothing reaches the server without passing your rules. This is the rule we recommend for pytest:
{
"version": "1",
"default": "deny",
"tools": {
"pytest": {
"limits": [
{
"counter": "pytest_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}pytest 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.
Free to start. No card required.
Runs pytest and returns structured test results (passed, failed, errors, skipped, failures). It is categorised as a Execute tool in the Lint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Lint MCP server in PolicyLayer and add a rule for pytest: 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 Lint. Nothing to install.
pytest 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 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. 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 is provided by the Lint MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Lint, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
202 Lint tools catalogued and risk-classified — across an index of 43,000+ MCP servers.