search_test_cases

THE RISK

Low Risk

Why search_test_cases needs a policy

This tool retrieves test case data based on search criteria. It performs a read-only query against the test management system with no capability to modify, delete, or execute anything. The blast radius of misuse is minimal — an AI agent could retrieve unintended test case information but cannot cause data loss, execute tests, or trigger external operations.

From the tool's definition Tool name is 'search_test_cases' and description explicitly states 'Search for test cases in a project' — a query operation with no modification or execution side effects.

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

POLICY

How to control search_test_cases

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 search_test_cases:

policy.json

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

search_test_cases 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 search_test_cases

What does the search_test_cases tool do? +

Search for test cases in a project. 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 search_test_cases? +

Register the JIRA Zephyr MCP Server MCP server in PolicyLayer and add a rule for search_test_cases: 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 search_test_cases? +

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

Can I rate-limit search_test_cases? +

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

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

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