回傳目前由 QA_RUNNER 環境變數選定的測試 runner（pytest / jest / cypress /
AI agents call get_runner_info to retrieve information from Mk Qa Master without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves the current state of the QA_RUNNER environment variable to report which test runner (pytest/jest/cypress/etc.) is active. It performs a read-only operation with no side effects, blast radius, or capability to modify system state. Classified as Read with low severity.
From the tool's definition Tool name 'get_runner_info' and description indicating it returns/retrieves information about the current test runner selected by an environment variable. No modification, execution, or deletion occurs.
Documented attack patterns abuse exactly the kind of access get_runner_info 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 get_runner_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_runner_info": {}
}
}get_runner_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
回傳目前由 QA_RUNNER 環境變數選定的測試 runner（pytest / jest / cypress /. It is categorised as a Read tool in the Mk Qa Master MCP Server, which means it retrieves data without modifying state.
Register the Mk Qa Master MCP server in PolicyLayer and add a rule for get_runner_info: 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.
get_runner_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_runner_info 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 get_runner_info. 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.
get_runner_info 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.