zephyr_get_test_cycles_linked_to_a_jira_issue

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/zephyr-get-test-cycles-linked-to-a-jira-issue.md

WHAT IT DOES

What zephyr_get_test_cycles_linked_to_a_jira_issue does on SmartBear MCP

AI agents call zephyr_get_test_cycles_linked_to_a_jira_issue 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
`issueKey`	string	Yes	The key of the Jira issue

Parameters from the server's own tool schema.

RISK

Why zephyr_get_test_cycles_linked_to_a_jira_issue is rated Low

This tool retrieves and queries existing test cycle data linked to a Jira issue with no side effects. It is a straightforward read operation that returns information without creating, modifying, deleting, or executing anything. The low severity reflects minimal blast radius if misused—an agent querying test cycles poses no destructive or operational risk.

From the tool's definition Tool name includes 'get' and description states 'Get test cycles linked to a Jira issue'; parameters are query-only (issueKey for lookup); expected output is 'list of test cycles' with no modification, deletion, or execution indicated.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

zephyr_get_test_cycles_linked_to_a_jira_issue Allowed

zephyr_get_test_cycles_linked_to_a_jira_issue 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_test_cycles_linked_to_a_jira_issue": {}
  }
}

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_test_cycles_linked_to_a_jira_issue call is checked against it from then on.

FAQ

Questions about zephyr_get_test_cycles_linked_to_a_jira_issue

What does the zephyr_get_test_cycles_linked_to_a_jira_issue tool do? +

Get test cycles linked to a Jira issue in Zephyr Parameters: - issueKey (string) *required*: The key of the Jira issue Examples: 1. Check which test cycles are linked to Jira issue PROJ-123 json { "issueKey": "PROJ-123" } Expected Output: The List of test cycles linked to Jira issue PROJ-123 with their IDs. 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_test_cycles_linked_to_a_jira_issue accept? +

zephyr_get_test_cycles_linked_to_a_jira_issue accepts 1 parameter: issueKey. Required: issueKey. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on zephyr_get_test_cycles_linked_to_a_jira_issue? +

Register the SmartBear MCP server in PolicyLayer and add a rule for zephyr_get_test_cycles_linked_to_a_jira_issue: 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_test_cycles_linked_to_a_jira_issue? +

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

Can I rate-limit zephyr_get_test_cycles_linked_to_a_jira_issue? +

Yes. Add a rate_limit block to the zephyr_get_test_cycles_linked_to_a_jira_issue 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_test_cycles_linked_to_a_jira_issue completely? +

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

zephyr_get_test_cycles_linked_to_a_jira_issue 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 →