Delete a test plan
AI agents call delete_plan 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.
This tool permanently removes a test plan and its associated data from TestRail, which cannot be undone. Deleting a test plan is a destructive operation that could cause loss of testing records, historical data, and project documentation. The high severity reflects the potential for significant operational impact if misused by an AI agent (e.g., deleting plans for active projects).
From the tool's definition Tool name is "delete_plan" with description "Delete a test plan". The verb "delete" indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a test plan. 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_plan: 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_plan 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_plan 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_plan. 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_plan 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 →