Delete a test plan entry
AI agents call delete_plan_entry 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 entry from TestRail, which cannot be undone. Deletion is irreversible data destruction, placing it in the Destructive category. The severity is high because accidental deletion of test plan entries could disrupt test management workflows and require restoration from backups. The confidence is high (0.95) because the intent is explicit in both the name and description.
From the tool's definition Tool name is 'delete_plan_entry' with description 'Delete a test plan entry'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a test plan entry. 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_entry: 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_entry 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_entry 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_entry. 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_entry 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 →