# 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}.

Agent View of the PolicyLayer registry record for `delete_test_case`. HTML page: https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/delete-test-case

## Facts

- Tool: `delete_test_case`
- Server: Debugg AI MCP (`debugg-ai/debugg-ai-mcp`) — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp.md
- Homepage: https://github.com/debugg-ai/debugg-ai-mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "delete_test_case",
    "arguments": {}
  }
}
```

## 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 own 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,…"

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Debugg AI MCP:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_test_case"
  ]
}
```

## Other tools on Debugg AI MCP (6)

- `delete_test_suite` — Destructive — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/delete-test-suite.md
- `run_test_suite` — Execute — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/run-test-suite.md
- `get_test_suite_results` — Read — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/get-test-suite-results.md
- `search_test_suites` — Read — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/search-test-suites.md
- `create_test_suite` — Write — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/create-test-suite.md
- `update_test_case` — Write — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/update-test-case.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=debugg-ai-debugg-ai-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/debugg-ai-debugg-ai-mcp