testgen_tdd_repair
ADR-175-inspired Test-Driven Repair. Use when you have a failing test and want a verified, bounded-cost fix. Spawns a bounded headless
This record as markdown: /tools/io-github-ruvnet-claude-flow/testgen-tdd-repair.md
What testgen_tdd_repair does on Claude Flow
AI agents invoke testgen_tdd_repair to trigger actions in Claude Flow. 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.
Why testgen_tdd_repair is rated High
The tool spawns external processes (headless environment) to analyze failing tests and apply fixes. This constitutes execution of code/scripts with side effects that depend on arguments. The blast radius is high because an AI agent could misuse it to run arbitrary repair logic or modify source code in unintended ways. The description is truncated, lowering confidence slightly.
From the tool's definition 'Spawns a bounded headless' (truncated) — the tool spawns a subprocess/headless environment to perform test-driven repair, executing code or scripts to fix failing tests
Attacks that exploit this kind of access
The rule that runs testgen_tdd_repair safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For testgen_tdd_repair, this is the rule to start with:
testgen_tdd_repair 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every testgen_tdd_repair call is checked against it from then on.
Questions about testgen_tdd_repair
ADR-175-inspired Test-Driven Repair. Use when you have a failing test and want a verified, bounded-cost fix. Spawns a bounded headless. It is categorised as a Execute tool in the Claude Flow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Flow MCP server in PolicyLayer and add a rule for testgen_tdd_repair: 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 Claude Flow. Nothing to install.
testgen_tdd_repair 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 testgen_tdd_repair 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 testgen_tdd_repair. 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.
testgen_tdd_repair is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Flow, and thousands of servers like it.
Across the catalogue