合并 TDD 工具。action: preset(查询预设)/step(单步执行)/loop(完整循环)/status(状态)/reset(重置)。
AI agents invoke qflow_tdd to trigger actions in Qflow. 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 runs TDD (Test-Driven Development) workflow actions including single-step execution and full loop cycles, which involve executing code or test processes. The 'reset' action modifies state. Overall the dominant behavior is triggering external operations (running tests/code), placing it in Execute.
From the tool's definition action: preset(查询预设)/step(单步执行)/loop(完整循环)/status(状态)/reset(重置) — 'step(单步执行)' and 'loop(完整循环)' indicate executing TDD steps/cycles, while 'reset(重置)' suggests state mutation
Documented attack patterns abuse exactly the kind of access qflow_tdd gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Qflow, and nothing reaches the server without passing your rules. This is the rule we recommend for qflow_tdd:
{
"version": "1",
"default": "deny",
"tools": {
"qflow_tdd": {
"limits": [
{
"counter": "qflow_tdd_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}qflow_tdd 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.
合并 TDD 工具。action: preset(查询预设)/step(单步执行)/loop(完整循环)/status(状态)/reset(重置)。. It is categorised as a Execute tool in the Qflow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Qflow MCP server in PolicyLayer and add a rule for qflow_tdd: 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 Qflow. Nothing to install.
qflow_tdd 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 qflow_tdd 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 qflow_tdd. 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.
qflow_tdd is provided by the Qflow MCP server (pangu-immortal/qflow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Qflow, 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.
50 Qflow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.