link_tests_to_issues

THE RISK

Medium Risk

Why link_tests_to_issues needs a policy

This tool creates associations/links between test cases and JIRA issues, which is a reversible write operation. It modifies relationship data in JIRA but does not delete or irreversibly alter existing records. Misuse could create incorrect traceability links, causing confusion in test coverage tracking, but it is not destructive or financial in nature.

From the tool's definition Associate test cases with JIRA issues

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

POLICY

How to control link_tests_to_issues

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "link_tests_to_issues": {
      "limits": [
        {
          "counter": "link_tests_to_issues_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

link_tests_to_issues stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. 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.

LIMIT 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 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 Read list_test_cycles List existing test cycles with execution status

All 13 JIRA Zephyr MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about link_tests_to_issues

What does the link_tests_to_issues tool do? +

Associate test cases with JIRA issues. It is categorised as a Write tool in the JIRA Zephyr MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on link_tests_to_issues? +

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

link_tests_to_issues is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit link_tests_to_issues? +

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

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

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