Delete a specific test case (Data Center only — not supported on Cloud v2)
AI agents call delete_test_case to permanently remove resources in Zephyr Scale 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 case from the test management system. Deletion operations are irreversible and cannot be undone, fitting the Destructive category. While the blast radius is limited to test case artifacts rather than production systems, the loss of test cases could impact testing integrity and historical records.
From the tool's definition Tool name is 'delete_test_case' and description states 'Delete a specific test case'. The verb 'delete' combined with the action of removing a test case indicates irreversible data destruction.
Attacks that exploit this kind of access
Delete a specific test case (Data Center only — not supported on Cloud v2). It is categorised as a Destructive tool in the Zephyr Scale MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Zephyr Scale MCP Server MCP server in PolicyLayer and add a rule for delete_test_case: 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 Zephyr Scale MCP Server. Nothing to install.
delete_test_case 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_test_case 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_test_case. 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_test_case is provided by the Zephyr Scale MCP Server MCP server (milo0821/zephyr_mcp_server). 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 →