create-test-cycle · qTest MCP Server MCP: Risk & Policy

WHAT IT DOES

What create-test-cycle does on qTest MCP Server

AI agents use create-test-cycle to create or update resources in qTest MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your qTest MCP Server environment.

WHY IT NEEDS A POLICY

Why create-test-cycle needs a policy

Creating a test cycle is a reversible modification operation (can be deleted via the sibling delete-test-cycle tool). It does not execute arbitrary code, delete data irreversibly, move money, or expose read-only access. The blast radius is limited to test management metadata within qTest.

From the tool's definition Tool name 'create-test-cycle' and description explicitly states it 'create[s] a test cycle' in qTest Test Execution. This is a data creation operation that modifies the qTest system state by adding a new execution folder/cycle.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create-test-cycle Rate-limited

create-test-cycle stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create-test-cycle": {
      "limits": [
        {
          "counter": "create-test-cycle_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches qTest MCP Server, so you can run agents against it safely.

FAQ

Questions about create-test-cycle

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

Test Execution — create a test cycle (execution folder) in qTest Test Execution to group test runs for a sprint, release, or regression campaign. It is categorised as a Write tool in the qTest MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create-test-cycle? +

Register the qTest MCP Server MCP server in PolicyLayer and add a rule for create-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 create-test-cycle? +

create-test-cycle is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create-test-cycle? +

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

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

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