Launch interactive test recording for the active runner. Useful as a
AI agents invoke codegen 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.
The tool launches an interactive recording session that drives external test runners (pytest, Jest, Cypress, etc.), triggering real operations in the environment. This is an execution action with potentially broad side effects depending on what is recorded and run. The description is incomplete ('Useful as a' is cut off), which lowers confidence slightly, but 'Launch' and 'interactive...
From the tool's definition "Launch interactive test recording for the active runner"
Documented attack patterns abuse exactly the kind of access codegen 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 codegen:
{
"version": "1",
"default": "deny",
"tools": {
"codegen": {
"limits": [
{
"counter": "codegen_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}codegen 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.
Launch interactive test recording for the active runner. Useful as a. 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 codegen: 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.
codegen 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 codegen 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 codegen. 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.
codegen 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.