# delete_test_suite

Disable (soft-delete) a test suite. The suite and its tests are hidden from default list queries but not permanently removed. Accepts suiteUuid directly, or suiteName + project identifier for name-based lookup. Returns {deleted: true, suiteUuid}.

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

## Facts

- Tool: `delete_test_suite`
- 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_suite",
    "arguments": {}
  }
}
```

## Why delete_test_suite is rated Critical

Although described as a 'soft-delete' (reversible in principle), the tool irreversibly removes a test suite from normal access and operations. It prevents the suite and its tests from appearing in standard queries, effectively taking it out of service. Even if data is technically recoverable at the database level, the tool's purpose is to delete/disable resources, placing it in the Destructive category.

From the tool's own definition: "Tool name 'delete_test_suite' combined with description stating it 'Disable (soft-delete) a test suite' and that 'The suite and its tests are hidden from default list queries but not permanently removed.' This is a deletion operation that removes test suites…"

## Use case

AI agents call delete_test_suite 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_suite"
  ]
}
```

## Other tools on Debugg AI MCP (6)

- `delete_test_case` — Destructive — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/delete-test-case.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