zephyr_get_test_cycle
Get details of test cycle specified by id or key in Zephyr Parameters: - testCycleIdOrKey (string) *required*: The ID or key of the test cycle. Examples: 1. Get the test cycle with id 1 json { "testCycleIdOrKey": "1" } Expected Output: The test cycle with its details 2. Get the test cycle with ke...
This record as markdown: /tools/smartbear-mcp/zephyr-get-test-cycle.md
What zephyr_get_test_cycle does on SmartBear MCP
AI agents call zephyr_get_test_cycle 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 |
|---|---|---|---|
testCycleIdOrKey | string | Yes | The ID or key of the test cycle. |
Parameters from the server's own tool schema.
Why zephyr_get_test_cycle is rated Low
This tool retrieves and returns test cycle metadata from Zephyr. It performs a lookup operation with no capability to create, modify, delete, or execute external operations. The blast radius of misuse is minimal — an agent could only access existing test cycle information, which does not compromise system integrity or enable destructive actions.
From the tool's definition Tool name 'zephyr_get_test_cycle' and description 'Get details of test cycle specified by id or key' indicates retrieval of test cycle information without modification.
Attacks that exploit this kind of access
The rule that runs zephyr_get_test_cycle 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_cycle, this is the rule to start with:
zephyr_get_test_cycle 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_cycle call is checked against it from then on.
Questions about zephyr_get_test_cycle
Get details of test cycle specified by id or key in Zephyr Parameters: - testCycleIdOrKey (string) *required*: The ID or key of the test cycle. Examples: 1. Get the test cycle with id 1 json { "testCycleIdOrKey": "1" } Expected Output: The test cycle with its details 2. Get the test cycle with key 'SA-R40' json { "testCycleIdOrKey": "SA-R40" } Expected Output: The test cycle 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_cycle accepts 1 parameter: testCycleIdOrKey. Required: testCycleIdOrKey. 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_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 SmartBear MCP. Nothing to install.
zephyr_get_test_cycle 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_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.
Set action: deny in the PolicyLayer policy for zephyr_get_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.
zephyr_get_test_cycle 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