zephyr_get_statuses

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Low RISK CLASS

Category Read

Parameters 40 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/zephyr-get-statuses.md

WHAT IT DOES

What zephyr_get_statuses does on SmartBear MCP

AI agents call zephyr_get_statuses 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
`statusType`	string	—	Determines which type of entity the status belongs to.

Parameters from the server's own tool schema.

RISK

Why zephyr_get_statuses is rated Low

This tool retrieves status information about test artifacts in Zephyr without modifying, deleting, or executing anything. It is a straightforward query operation with pagination support. The blast radius of misuse is minimal—an agent could retrieve unwanted status information but cannot cause side effects or damage.

From the tool's definition Tool name 'zephyr_get_statuses' and description 'Get statuses of different types of test artifacts in Zephyr' indicate a retrieval operation. Parameters include 'maxResults' and 'startAt' which are pagination/query filters typical of read operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs zephyr_get_statuses 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_statuses, this is the rule to start with:

zephyr_get_statuses Allowed

zephyr_get_statuses is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "zephyr_get_statuses": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every zephyr_get_statuses call is checked against it from then on.

FAQ

Questions about zephyr_get_statuses

What does the zephyr_get_statuses tool do? +

Get statuses of different types of test artifacts in Zephyr Parameters: - 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) - projectKey (string): Jira project key filter - statusType (enum): Determines which type of entity the status belongs to. Examples: 1. Get the first 10 statuses json { "maxResults": 10, "startAt": 0 } Expected Output: The first 10 statuses with their details from different projects and test artifact types 2. Get 10 test case statuses json { "maxResults": 10, "statusType": "TEST_CASE" } Expected Output: A list of statuses related to test cases with their details 3. Get five statuses from the project PROJ json { "maxResults": 5, "projectKey": "PROJ" } Expected Output: The first five statuses 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.

What parameters does zephyr_get_statuses accept? +

zephyr_get_statuses accepts 4 parameters: startAt, maxResults, projectKey, statusType. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on zephyr_get_statuses? +

Register the SmartBear MCP server in PolicyLayer and add a rule for zephyr_get_statuses: 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.

What risk level is zephyr_get_statuses? +

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

Can I rate-limit zephyr_get_statuses? +

Yes. Add a rate_limit block to the zephyr_get_statuses 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.

How do I block zephyr_get_statuses completely? +

Set action: deny in the PolicyLayer policy for zephyr_get_statuses. 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 zephyr_get_statuses? +

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

KEEP EXPLORING

More on SmartBear, and thousands of servers like it.

This server

All 240 SmartBear tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →