Dynamically import a module export that builds a fast-check property and assert it.
AI agents invoke tdd_property_check 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 dynamically imports and executes arbitrary module code to run property-based tests. 'Dynamically import a module export' means it loads and executes code at runtime, which constitutes code execution. The blast radius is high because an AI agent could point it at malicious or destructive modules, causing arbitrary code execution on the host system.
From the tool's definition Dynamically import a module export that builds a fast-check property and assert it
Attacks that exploit this kind of access
Dynamically import a module export that builds a fast-check property and assert it. 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_property_check: 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_property_check 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_property_check 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_property_check. 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_property_check 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 →