Create or append a test file next to a module (unit or property-test template).
AI agents use tdd_scaffold_test to create or update resources in Promethean OS MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Promethean OS MCP environment.
This tool creates or modifies test files on the filesystem. 'Create or append' indicates a reversible write operation — it does not delete or overwrite destructively, nor does it execute code. Severity is medium because writing files to arbitrary locations could have meaningful impact if misused, but the scope is limited to test scaffolding templates.
From the tool's definition Create or append a test file next to a module
Attacks that exploit this kind of access
Create or append a test file next to a module (unit or property-test template). It is categorised as a Write tool in the Promethean OS MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Promethean OS MCP server in PolicyLayer and add a rule for tdd_scaffold_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 Promethean OS MCP. Nothing to install.
tdd_scaffold_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 tdd_scaffold_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 tdd_scaffold_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.
tdd_scaffold_test 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 →