Execute a single test case via FastAPI to ensure execution is tracked.
AI agents invoke run_case to trigger actions in OpenTester. 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.
This tool triggers external operations (test execution via FastAPI) whose side effects are determined by the arguments (which test case is run). Test execution can have broad system impacts including file I/O, network calls, and state changes depending on what the test does. While not inherently destructive or financial, the blast radius if an agent runs malicious or poorly-constructed test cases is significant.
From the tool's definition Tool description states 'Execute a single test case via FastAPI' - the verb 'Execute' combined with 'via FastAPI' indicates this runs code/test execution whose effects depend on the test case arguments provided.
Documented attack patterns abuse exactly the kind of access run_case gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenTester, and nothing reaches the server without passing your rules. This is the rule we recommend for run_case:
{
"version": "1",
"default": "deny",
"tools": {
"run_case": {
"limits": [
{
"counter": "run_case_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_case 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.
Execute a single test case via FastAPI to ensure execution is tracked. It is categorised as a Execute tool in the OpenTester MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OpenTester MCP server in PolicyLayer and add a rule for run_case: 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 OpenTester. Nothing to install.
run_case 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_case 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_case. 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_case is provided by the OpenTester MCP server (kznr02/opentester). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OpenTester, 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.
23 OpenTester tools catalogued and risk-classified — across an index of 43,000+ MCP servers.