create_test_cycle · Zephyr Scale MCP Server MCP

WHAT IT DOES

What create_test_cycle does on Zephyr Scale MCP Server

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

WHY IT NEEDS A POLICY

Why create_test_cycle needs a policy

Test cycle creation in Zephyr Scale is a write operation that creates new test management entities. While the description is empty (lowering confidence slightly), the tool name and server context are clear. This is Write rather than Read (creates data), Execute (no code/shell execution), Destructive (reversible), or Financial (no monetary impact).

From the tool's definition Tool name is 'create_test_cycle' with no description provided; however, context from sibling tools (create_test_case, create_test_execution, create_environment, etc.) and server description establishes this is a test management API that creates data.

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 Zephyr Scale MCP Server, so you can run agents against it safely.

FAQ

Questions about create_test_cycle

What does the create_test_cycle tool do? +

create_test_cycle. It is categorised as a Write tool in the Zephyr Scale 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 Zephyr Scale 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 Zephyr Scale 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 Zephyr Scale MCP Server MCP server (metquay/zephyr-scale-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.