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}.
This record as markdown: /tools/debugg-ai-debugg-ai-mcp/delete-test-suite.md
What delete_test_suite does on Debugg AI MCP
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.
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 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…
Attacks that exploit this kind of access
The rule that runs delete_test_suite 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_suite, this is the rule to start with:
delete_test_suite 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_suite call is checked against it from then on.
Questions about 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}. 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_suite: 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_suite 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_suite 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_suite. 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_suite 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