// SCAN REPORT

Zephyr Scale MCP Server

45 tools. 18 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 29 Jun 2026

18 can modify or destroy data

27 read-only

45 tools total

Community server · catalogue entry verified 29/06/2026

How to control Zephyr Scale MCP Server ↓

TOOL MAP

What Zephyr Scale MCP Server exposes to your agents

Read (27) Write / Execute (17) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Zephyr Scale MCP Server tools

Destructive · High delete_link The tool performs an irreversible deletion operation. Write · Medium create_environment This tool creates a new environment entity, which is a reversible write operation. Write · Low create_folder This tool creates a new folder within the test management hierarchy—a reversible operation that adds structure without modifying, executing, deleting, or moving data. Write · Low create_priority This tool creates a new priority record in Zephyr Scale, which is a reversible write operation.

18 of Zephyr Scale MCP Server's 45 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Zephyr Scale MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Zephyr Scale MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_link": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "create_environment": {
    "limits": [
      {
        "counter": "create_environment_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_api_info": {
    "limits": [
      {
        "counter": "get_api_info_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Zephyr Scale MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON ZEPHYR SCALE →

Instant setup, no code required.

FULL CATALOGUE

All 45 Zephyr Scale MCP Server tools

DESTRUCTIVE 1 tools

Destructive delete_link Delete a link by ID.

WRITE 17 tools

Write create_environment Create a new environment. Write create_folder Create a new folder. Write create_priority Create a new priority. Write create_status create_status Write create_test_case create_test_case Write create_test_case_issue_link Create a link between a test case and a Jira issue. Write create_test_case_script Create or update a test script for a test case. Write create_test_case_steps Create test steps for a test case. Write create_test_case_web_link Create a web link for a test case. Write create_test_cycle create_test_cycle Write create_test_execution create_test_execution Write update_environment Update an existing environment. Write update_priority Update an existing priority. Write update_status Update an existing status. Write update_test_case Update an existing test case. Write update_test_cycle Update an existing test cycle. Write update_test_execution Update an existing test execution.

READ 27 tools

Read get_api_info Get information about the Zephyr Scale MCP server configuration. Read get_environment Get a specific environment by ID. Read get_environments Get environments from Zephyr Scale. Read get_folder Get a specific folder by ID. Read get_folders get_folders Read get_issue_link_test_cases Get test case keys and versions linked to a Jira issue. Read get_issue_link_test_cycles Get test cycle IDs linked to a Jira issue. Read get_issue_link_test_executions Get test execution IDs linked to a Jira issue. Read get_issue_link_test_plans Get test plan IDs linked to a Jira issue. Read get_priorities Get priorities from Zephyr Scale. Read get_priority Get a specific priority by ID. Read get_project Get a specific project by ID or key. Read get_projects Get all projects from Zephyr Scale. Read get_status Get a specific status by ID. Read get_statuses get_statuses Read get_test_case Get a specific test case by key. Read get_test_case_links Get all links for a test case. Read get_test_case_script Get the test script for a test case. Read get_test_case_steps Get test steps for a test case. Read get_test_case_version Get a specific version of a test case. Read get_test_case_versions Get all versions of a test case. Read get_test_cases get_test_cases Read get_test_cycle Get a specific test cycle by ID or key. Read get_test_cycles get_test_cycles Read get_test_execution Get a specific test execution by ID or key. Read get_test_executions get_test_executions Read health_check Check the health of the Zephyr Scale API.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Zephyr Scale MCP Server

Can an AI agent delete data through the Zephyr Scale MCP Server MCP server? +

Yes. The Zephyr Scale MCP Server server exposes 1 destructive tools including delete_link. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Zephyr Scale MCP Server? +

The Zephyr Scale MCP Server server has 17 write tools including create_environment, create_folder, create_priority. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Zephyr Scale MCP Server.

How many tools does the Zephyr Scale MCP Server MCP server expose? +

45 tools across 3 categories: Destructive, Read, Write. 27 are read-only. 18 can modify, create, or delete data.

How do I enforce a policy on Zephyr Scale MCP Server? +

Register the Zephyr Scale MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Zephyr Scale MCP Server tool call.

Deterministic rules across all 45 Zephyr Scale MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON ZEPHYR SCALE →

Instant setup, no code required.

45 Zephyr Scale MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.