New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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

SERVERDebugg AI MCP SOURCEdebugg-ai/debugg-ai-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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…

Questions about delete_test_suite

What does the delete_test_suite tool do? +

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.

How do I enforce a policy on delete_test_suite? +

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.

What risk level is delete_test_suite? +

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.

Can I rate-limit delete_test_suite? +

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.

How do I block delete_test_suite completely? +

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.

What MCP server provides delete_test_suite? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Debugg AI's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.