qmetry_fetch_releases_and_cycles

// WHEN AI AGENTS USE THIS TOOL

AI agents call qmetry_fetch_releases_and_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 QMETRY_FETCH_RELEASES_AND_CYCLES

Even though qmetry_fetch_releases_and_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:
  qmetry_fetch_releases_and_cycles:
    rules:
      - action: allow

See the full SmartBear MCP policy for all 147 tools.

// DETAILS

Tool Name qmetry_fetch_releases_and_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 qmetry_fetch_releases_and_cycles tool do? +

Fetch QMetry releases and cycles from the current project **Parameters:** - projectKey (string): Project key - unique identifier for the project (default: "default") - showArchive (boolean): Whether to include archived records in the results. When true, returns both active and archived items. When false, returns only active (non-archived) items. Applies to any entity type being fetched (test cases, requirements, releases, cycles, builds, platforms, etc.). **Output Description:** JSON object with project hierarchy containing releases and their associated cycles **Use Cases:** 1. Fetch associated releases and cycles of current project 2. Fetch available releases and cycles of current project 3. Get release and cycle information for test planning 4. List all releases and cycles in a project 5. Search for specific releases using release name or ID 6. Fetch cycle lists based on release ID 7. Search for specific cycles using cycle name or ID 8. Get project structure for test planning and execution 9. Retrieve release hierarchy for reporting purposes **Examples:** 1. Get active releases and cycles (default behavior) ```json {} ``` Expected Output: List of active releases and cycles excluding archived ones (showArchive: false sent in payload) 2. Get active/unarchived releases and cycles explicitly ```json { "showArchive": false } ``` Expected Output: List of active releases and cycles excluding archived ones (showArchive: false sent in payload) 3. Get not active/archived releases and cycles ```json { "showArchive": true } ``` Expected Output: List of all releases and cycles including archived ones (showArchive: true sent in payload) **Hints:** 1. Use 'default' project key when user doesn't specify one 2. PAYLOAD SCENARIOS: 3. - No showArchive parameter → payload: {showArchive: false} → Returns only active releases/cycles 4. - showArchive: false → payload: {showArchive: false} → Returns only active/non-archived releases/cycles 5. - showArchive: true → payload: {showArchive: true} → Returns all releases/cycles including archived ones 6. Default behavior always excludes archived items unless explicitly requested 7. Releases contain cycles - use this hierarchy for test execution planning 8. Each release can have multiple cycles representing different testing phases. 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 qmetry_fetch_releases_and_cycles? +

Add a rule in your Intercept YAML policy under the tools section for qmetry_fetch_releases_and_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 qmetry_fetch_releases_and_cycles? +

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

Can I rate-limit qmetry_fetch_releases_and_cycles? +

Yes. Add a rate_limit block to the qmetry_fetch_releases_and_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 qmetry_fetch_releases_and_cycles completely? +

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

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

qmetry_fetch_releases_and_cycles

Enforce policies on SmartBear MCP