delete_test_case
Disable (soft-delete) a test case. The test is hidden from default list queries but not permanently removed. Requires testUuid. Returns {deleted: true, testUuid}.
This record as markdown: /tools/debugg-ai-debugg-ai-mcp/delete-test-case.md
What delete_test_case does on Debugg AI MCP
AI agents call delete_test_case to permanently remove resources in Debugg AI MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_test_case is rated Critical
Although described as a 'soft-delete' (logically reversible), the tool is explicitly named 'delete' and performs an irreversible removal operation—hiding the test case from default queries and making it inaccessible through normal workflows. This matches the Destructive category: actions that cannot be undone in practice without administrative intervention.
From the tool's definition Tool name: 'delete_test_case'. Description: 'Disable (soft-delete) a test case. The test is hidden from default list queries but not permanently removed.' The action is irreversible in the sense that it removes the test case from normal visibility and access,…
Attacks that exploit this kind of access
The rule that runs delete_test_case safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Debugg AI MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_test_case, this is the rule to start with:
delete_test_case is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Debugg AI MCP, apply this rule, and every delete_test_case call is checked against it from then on.
Questions about delete_test_case
Disable (soft-delete) a test case. The test is hidden from default list queries but not permanently removed. Requires testUuid. Returns {deleted: true, testUuid}. It is categorised as a Destructive tool in the Debugg AI MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Debugg AI 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 Debugg AI MCP. 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 Debugg AI MCP server (debugg-ai/debugg-ai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Debugg AI, and thousands of servers like it.
Across the catalogue