AI agents use record_test_outcome to create or update resources in MCP Pytest Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Pytest Server environment.
This tool writes test outcome data to some store (likely a database or log). It creates/modifies a record of a test result, which is a reversible write operation with low blast radius. It does not execute code, delete data, or involve financial transactions.
From the tool's definition 'Record the outcome of a test' — records/writes test result data
Documented attack patterns abuse exactly the kind of access record_test_outcome gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Pytest Server, and nothing reaches the server without passing your rules. This is the rule we recommend for record_test_outcome:
{
"version": "1",
"default": "deny",
"tools": {
"record_test_outcome": {
"limits": [
{
"counter": "record_test_outcome_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}record_test_outcome stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Record the outcome of a test. It is categorised as a Write tool in the MCP Pytest Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Pytest Server MCP server in PolicyLayer and add a rule for record_test_outcome: 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 MCP Pytest Server. Nothing to install.
record_test_outcome is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the record_test_outcome 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 record_test_outcome. 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.
record_test_outcome is provided by the MCP Pytest Server MCP server (kieranlal/mcp_pytest_service). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Pytest Server, 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.
3 MCP Pytest Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.