Delete multiple test cases
AI agents call delete_cases to permanently remove resources in TestRail MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of test cases cannot be undone and represents permanent loss of test data and associated metadata. While not a financial or code-execution risk, this is a destructive operation affecting the integrity of the test management system. The ability to delete multiple cases in a batch amplifies the blast radius if misused by an AI agent.
From the tool's definition Tool name is 'delete_cases' and description states 'Delete multiple test cases' — the verb 'delete' combined with the plural scope indicates irreversible removal of test case data.
Attacks that exploit this kind of access
Delete multiple test cases. It is categorised as a Destructive tool in the TestRail MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TestRail MCP Server MCP server in PolicyLayer and add a rule for 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 TestRail MCP Server. Nothing to install.
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 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 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.
delete_cases is provided by the TestRail MCP Server MCP server (tenbarrel6/testrail-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 →