Execute the test suite under the active QA_RUNNER and produce a structured
AI agents invoke run_tests to trigger actions in Mk Qa Master. 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) whose side effects are determined by the test suite contents and runtime environment. While tests are typically benign, a compromised or malicious test suite could modify data, make network calls, or affect system state.
From the tool's definition Tool name 'run_tests' and description states 'Execute the test suite' — this runs test code whose effects depend on test configuration and environment state.
Documented attack patterns abuse exactly the kind of access run_tests gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mk Qa Master, and nothing reaches the server without passing your rules. This is the rule we recommend for run_tests:
{
"version": "1",
"default": "deny",
"tools": {
"run_tests": {
"limits": [
{
"counter": "run_tests_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_tests 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 the test suite under the active QA_RUNNER and produce a structured. It is categorised as a Execute tool in the Mk Qa Master MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mk Qa Master MCP server in PolicyLayer and add a rule for run_tests: 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 Mk Qa Master. Nothing to install.
run_tests 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_tests 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_tests. 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_tests is provided by the Mk Qa Master MCP server (kao273183/mk-qa-master). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mk Qa Master, 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.
22 Mk Qa Master tools catalogued and risk-classified — across an index of 43,000+ MCP servers.