Delete multiple test cases (max 100 per call).
AI agents call testmo_batch_delete_cases to permanently remove resources in Testmo — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes test cases from the Testmo test management system. Deletion of test cases is an irreversible operation that destroys data and cannot be recovered. The ability to delete up to 100 cases per call represents a significant blast radius. This is a Destructive action, which takes precedence over Write category actions.
From the tool's definition Tool name contains 'delete' and description states 'Delete multiple test cases (max 100 per call).' Deletion is irreversible and cannot be undone.
Attacks that exploit this kind of access
Delete multiple test cases (max 100 per call). It is categorised as a Destructive tool in the Testmo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Testmo MCP server in PolicyLayer and add a rule for testmo_batch_delete_cases: 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 Testmo. Nothing to install.
testmo_batch_delete_cases is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the testmo_batch_delete_cases 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 testmo_batch_delete_cases. 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.
testmo_batch_delete_cases is provided by the Testmo MCP server (strelec00/testmo-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 →