AI agents use generate_test 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.
This tool creates test code files, which is a reversible write operation. It does not execute tests (that would be Execute), nor does it delete or modify existing data irreversibly (not Destructive). The severity is medium because generated test files could introduce bugs or be used to create malicious test cases that might affect QA workflows, but the operation itself is reversible.
From the tool's definition Tool name 'generate_test' and description indicate it generates test code ('pytest-playwright 測試骨架' = pytest-playwright test scaffold). Generating test files creates new data artifacts.
Documented attack patterns abuse exactly the kind of access generate_test 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 generate_test:
{
"version": "1",
"default": "deny",
"tools": {
"generate_test": {
"limits": [
{
"counter": "generate_test_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}generate_test 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.
產生 pytest-playwright 測試骨架。. 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 generate_test: 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.
generate_test 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 generate_test 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 generate_test. 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.
generate_test 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.