list_test_cycles

THE RISK

Low Risk

Why list_test_cycles needs a policy

This tool retrieves and displays existing test cycle data and their execution statuses. It has no side effects, does not create, modify, delete, or execute anything—it only queries and returns information. This is a straightforward Read category operation with low severity since any misuse would only expose test planning metadata without affecting systems or data integrity.

From the tool's definition Tool name 'list_test_cycles' and description 'List existing test cycles with execution status' indicate retrieval of data without modification. The verb 'list' is a classic Read operation that queries and returns information.

Documented attack patterns abuse exactly the kind of access list_test_cycles gives an agent:

POLICY

How to control list_test_cycles

PolicyLayer is an MCP gateway — it sits between your AI agents and JIRA Zephyr MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_test_cycles:

policy.json

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

list_test_cycles is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register JIRA Zephyr MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More JIRA Zephyr MCP Server tools

Write execute_test Update test execution results Write link_tests_to_issues Associate test cases with JIRA issues Write create_multiple_test_cases Create multiple test cases in Zephyr at once Write create_test_case Create a new test case in Zephyr Write create_test_cycle Create a new test execution cycle Write create_test_plan Create a new test plan in Zephyr Read get_test_case Get detailed information about a specific test case Read get_test_execution_status Get test execution progress and statistics

All 13 JIRA Zephyr MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about list_test_cycles

What does the list_test_cycles tool do? +

List existing test cycles with execution status. It is categorised as a Read tool in the JIRA Zephyr MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_test_cycles? +

Register the JIRA Zephyr MCP Server MCP server in PolicyLayer and add a rule for list_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 JIRA Zephyr MCP Server. Nothing to install.

What risk level is list_test_cycles? +

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

Can I rate-limit list_test_cycles? +

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

How do I block list_test_cycles completely? +

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

What MCP server provides list_test_cycles? +

list_test_cycles is provided by the JIRA Zephyr MCP Server MCP server (leorosignoli/jira-zephyr-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every JIRA Zephyr MCP Server tool call.

Start from JIRA Zephyr MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →