v0.9.1 — Store a critical-points checklist before acting on a QA
AI agents use qa_plan to create or update resources in Mk Qa Master — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mk Qa Master environment.
The tool stores/persists a checklist (QA plan), which is a write operation creating or modifying data. It does not execute tests, delete data, or involve financial operations. Severity is medium since a misconfigured QA plan could misdirect subsequent test execution across the QA loop, but the tool itself only stores data.
From the tool's definition Store a critical-points checklist before acting on a QA
Documented attack patterns abuse exactly the kind of access qa_plan 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 qa_plan:
{
"version": "1",
"default": "deny",
"tools": {
"qa_plan": {
"limits": [
{
"counter": "qa_plan_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}qa_plan 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.
v0.9.1 — Store a critical-points checklist before acting on a QA. It is categorised as a Write tool in the Mk Qa Master MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mk Qa Master MCP server in PolicyLayer and add a rule for qa_plan: 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.
qa_plan 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 qa_plan 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 qa_plan. 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.
qa_plan 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.