zephyr_get_environments
Get environments in Zephyr Parameters: - projectKey (string): Jira project key 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 server may enforce a lower l...
This record as markdown: /tools/smartbear-mcp/zephyr-get-environments.md
What zephyr_get_environments does on SmartBear MCP
AI agents call zephyr_get_environments 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. |
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 |
Parameters from the server's own tool schema.
Why zephyr_get_environments is rated Low
This tool retrieves or queries environment data from Zephyr (a test management tool) without performing any side effects. It supports pagination and filtering but does not create, modify, delete, or execute operations. It is purely informational/read-only, hence the Read category with low severity.
From the tool's definition Tool name is 'zephyr_get_environments' and description states 'Get environments in Zephyr'. Parameters include 'projectKey' filter, 'maxResults', and 'startAt' (pagination), which are characteristic of read/query operations.
Attacks that exploit this kind of access
The rule that runs zephyr_get_environments 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_environments, this is the rule to start with:
zephyr_get_environments 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_environments call is checked against it from then on.
Questions about zephyr_get_environments
Get environments in Zephyr Parameters: - projectKey (string): Jira project key 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 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 20 Environments json { "maxResults": 20, "startAt": 0 } Expected Output: The first 20 Environments with their details from different projects 2. Get the first 10 Environments from the project with projectKey TEST json { "projectKey": "TEST", "maxResults": 10, "startAt": 0 } Expected Output: The first 10 Environments with their details from project with projectKey TEST 3. Get second 10 Environments from the project with projectKey TEST json { "projectKey": "TEST", "maxResults": 10, "startAt": 10 } Expected Output: The second 10 Environments with their details from project with projectKey TEST 4. Get Environments starting from the 5th Environment from different projects json { "startAt": 5, "maxResults": 10 } Expected Output: Environments starting from the 5th one with their details from different projects 5. Get 5 Environments starting from the 10th Environment from the project with projectKey PROJ json { "startAt": 10, "maxResults": 5, "projectKey": "PROJ" } Expected Output: The five environments starting from the 10th Environment from the project PROJ with their details. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
zephyr_get_environments accepts 3 parameters: startAt, maxResults, projectKey. 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_environments: 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_environments 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_environments 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_environments. 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_environments 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