Run Stryker mutation testing and return the score (fail if below minScore).
AI agents invoke tdd_mutation_score to trigger actions in Promethean OS MCP. 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.
This tool invokes Stryker, an external mutation testing framework that modifies code, runs tests, and generates metrics. While the end result is a report (Read-like output), the action itself is Execute: it triggers subprocess execution with side effects (CPU usage, test execution, file system operations).
From the tool's definition "Run Stryker mutation testing" - executes mutation testing framework with externally observable effects (test suite execution, code modification).
Attacks that exploit this kind of access
Run Stryker mutation testing and return the score (fail if below minScore). It is categorised as a Execute tool in the Promethean OS MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Promethean OS MCP server in PolicyLayer and add a rule for tdd_mutation_score: 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 Promethean OS MCP. Nothing to install.
tdd_mutation_score 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 tdd_mutation_score 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 tdd_mutation_score. 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.
tdd_mutation_score is provided by the Promethean OS MCP server (octave-commons/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →