qmetry_fetch_releases_and_cycles
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 fa...
This record as markdown: /tools/smartbear-mcp/qmetry-fetch-releases-and-cycles.md
What qmetry_fetch_releases_and_cycles does on SmartBear MCP
AI agents call qmetry_fetch_releases_and_cycles to retrieve information from SmartBear MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
projectKey | string | — | Project key - unique identifier for the project |
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. App |
Parameters from the server's own tool schema.
Why qmetry_fetch_releases_and_cycles is rated Low
This tool retrieves and queries project hierarchy data (releases and cycles) with no side effects or ability to create, modify, or delete data. It is a straightforward read operation that returns structured information based on filter parameters.
From the tool's definition Tool name contains 'fetch' and description states 'Fetch QMetry releases and cycles from the current project'. Parameters include optional filtering (projectKey, showArchive) but no modification capability.
Attacks that exploit this kind of access
The rule that runs qmetry_fetch_releases_and_cycles safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SmartBear MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For qmetry_fetch_releases_and_cycles, this is the rule to start with:
qmetry_fetch_releases_and_cycles is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every qmetry_fetch_releases_and_cycles call is checked against it from then on.
Questions about qmetry_fetch_releases_and_cycles
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.
qmetry_fetch_releases_and_cycles accepts 2 parameters: projectKey, showArchive. The full parameter table on this page comes from the server's own tool schema.
Register the SmartBear MCP server in PolicyLayer and add a rule for qmetry_fetch_releases_and_cycles: 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 SmartBear MCP. Nothing to install.
qmetry_fetch_releases_and_cycles is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the qmetry_fetch_releases_and_cycles 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.
Set action: deny in the PolicyLayer 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.
qmetry_fetch_releases_and_cycles is provided by the SmartBear MCP server (SmartBear/smartbear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SmartBear, and thousands of servers like it.
This server
Across the catalogue