zephyr_get_test_cycles

// WHEN AI AGENTS USE THIS TOOL

AI agents call zephyr_get_test_cycles to retrieve information from SmartBear MCP without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON ZEPHYR_GET_TEST_CYCLES

Even though zephyr_get_test_cycles only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

smartbear-mcp.yaml

tools:
  zephyr_get_test_cycles:
    rules:
      - action: allow

See the full SmartBear MCP policy for all 147 tools.

// DETAILS

Tool Name zephyr_get_test_cycles

Category Read

MCP Server SmartBear MCP MCP Server

Risk Level Low

// MORE SMARTBEAR MCP TOOLS

Destructive collaborator_delete_collaborator_remote_system_configuration Destructive reflect_cancel_suite_execution Destructive reflect_delete_previous_step Destructive swagger_delete_portal_product Destructive swagger_delete_table_of_contents Execute collaborator_reviewservice_action Execute contract-testing_can_i_deploy Execute qmetry_link_issues_to_testcase_run

View all 147 tools →

// RELATED READING

// FAQ

What does the zephyr_get_test_cycles tool do? +

Get details of Test Cycles in Zephyr **Parameters:** - projectKey (string): Jira project key filter - folderId (number): Folder ID filter - jiraProjectVersionId (number): Jira Project Version ID. Relates to 'Version' or 'Releases' in Jira projects. - maxResults (number): Specifies the maximum number of results to return in a single call. The default value is 10, and the maximum value that can be requested is 1000. Note that the server may enforce a lower limit than requested, depending on resource availability or other internal constraints. If this happens, the result set may be truncated. Always check the maxResults value in the response to confirm how many results were actually returned. (default: 10) - startAt (number): Zero-indexed starting position. Should be a multiple of maxResults. (default: 0) **Examples:** 1. Get the first 10 Test Cycles ```json { "maxResults": 10, "startAt": 0 } ``` Expected Output: The first 10 Test Cycles with their details 2. Get any Test Cycle ```json { "maxResults": 1 } ``` Expected Output: One Test Cycle with its details 3. Get five Test Cycles starting from the 7th Test Cycles of the list ```json { "maxResults": 5, "startAt": 6 } ``` Expected Output: The 7th to the 11th Test Cycles with their details 4. Get one Test Cycle from the project PROJ ```json { "projectKey": "PROJ", "maxResults": 1 } ``` Expected Output: One Test Cycle from project PROJ with its details 5. Get one Test Cycle from the folder with ID 123 ```json { "folderId": 123, "maxResults": 1 } ``` Expected Output: One Test Cycle from folder with ID 123 with its details 6. Get one Test Cycle from the version 456 ```json { "jiraProjectVersionId": 456, "maxResults": 1 } ``` Expected Output: One Test Cycle from version 456 with its details. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on zephyr_get_test_cycles? +

Add a rule in your Intercept YAML policy under the tools section for zephyr_get_test_cycles. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the SmartBear MCP MCP server.

What risk level is zephyr_get_test_cycles? +

zephyr_get_test_cycles is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit zephyr_get_test_cycles? +

Yes. Add a rate_limit block to the zephyr_get_test_cycles rule in your Intercept 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 zephyr_get_test_cycles completely? +

Set action: deny in the Intercept policy for zephyr_get_test_cycles. 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 zephyr_get_test_cycles? +

zephyr_get_test_cycles is provided by the SmartBear MCP MCP server (@smartbear/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on SmartBear MCP