zephyr_get_test_cycles
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 ...
This record as markdown: /tools/smartbear-mcp/zephyr-get-test-cycles.md
What zephyr_get_test_cycles does on SmartBear MCP
AI agents call zephyr_get_test_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 |
|---|---|---|---|
startAt | number | — | Zero-indexed starting position. Should be a multiple of maxResults. |
folderId | number | — | Folder ID filter |
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 |
projectKey | string | — | Jira project key filter |
jiraProjectVersionId | number | — | Jira Project Version ID. Relates to 'Version' or 'Releases' in Jira projects. |
Parameters from the server's own tool schema.
Why zephyr_get_test_cycles is rated Low
This tool retrieves test cycle information from Zephyr (a test management tool) with read-only operations. It queries and filters existing data without modifying, deleting, or executing any operations. The maxResults parameter for pagination further confirms this is a simple data retrieval function with no side effects.
From the tool's definition Tool name includes 'get_test_cycles' with description 'Get details of Test Cycles in Zephyr'. Parameters include filtering options (projectKey, folderId, jiraProjectVersionId) and result pagination (maxResults), all consistent with data retrieval.
Attacks that exploit this kind of access
The rule that runs zephyr_get_test_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 zephyr_get_test_cycles, this is the rule to start with:
zephyr_get_test_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 zephyr_get_test_cycles call is checked against it from then on.
Questions about zephyr_get_test_cycles
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.
zephyr_get_test_cycles accepts 5 parameters: startAt, folderId, maxResults, projectKey, jiraProjectVersionId. 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 zephyr_get_test_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.
zephyr_get_test_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 zephyr_get_test_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 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.
zephyr_get_test_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