delete-test-cycle

Test Execution — delete a qTest test cycle by numeric id. Cascades to all child test cycles, test suites, and test runs automatically.

Server qTest MCP Server usman-ghani123/qtest-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What delete-test-cycle does on qTest MCP Server

AI agents call delete-test-cycle to permanently remove resources in qTest MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete-test-cycle needs a policy

This tool performs irreversible deletion with cascading effects across related test artifacts. Once deleted, the test cycle and all its child objects (cycles, suites, runs) are permanently removed, which is the definition of Destructive. The cascading nature amplifies the blast radius, as a single invocation can eliminate large volumes of test data and related execution records.

From the tool's definition 'delete a qTest test cycle by numeric id. Cascades to all child test cycles, test suites, and test runs automatically.' — the tool irreversibly deletes data and automatically cascades deletion to dependent objects (child cycles, suites, runs), making this…

Questions about delete-test-cycle

What does the delete-test-cycle tool do? +

Test Execution — delete a qTest test cycle by numeric id. Cascades to all child test cycles, test suites, and test runs automatically. It is categorised as a Destructive tool in the qTest MCP Server 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-cycle? +

Register the qTest MCP Server MCP server in PolicyLayer and add a rule for delete-test-cycle: 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 qTest MCP Server. Nothing to install.

What risk level is delete-test-cycle? +

delete-test-cycle 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-cycle? +

Yes. Add a rate_limit block to the delete-test-cycle 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-cycle completely? +

Set action: deny in the PolicyLayer policy for delete-test-cycle. 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-cycle? +

delete-test-cycle is provided by the qTest MCP Server MCP server (usman-ghani123/qtest-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.