zephyr_create_test_execution_issue_link

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/zephyr-create-test-execution-issue-link.md

WHAT IT DOES

What zephyr_create_test_execution_issue_link does on SmartBear MCP

AI agents use zephyr_create_test_execution_issue_link to create or update resources in SmartBear MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SmartBear MCP environment.

Parameter	Type	Required	Description
`issueId`	number	Yes	The Jira issue ID
`testExecutionIdOrKey`	string	Yes	The ID or key of the test execution. Test execution keys are of the format [A-Z]+-E[0-9]+

Parameters from the server's own tool schema.

RISK

Why zephyr_create_test_execution_issue_link is rated Medium

This tool creates new data (a link/association) in Zephyr and Jira systems. It is reversible—the link can be deleted or modified later. The impact is localized to test execution metadata and does not involve destructive operations, code execution, or financial transactions.

From the tool's definition Tool name contains 'create' and description states 'Create a new link between a Jira issue and a Test Execution in Zephyr'. The examples show the tool creates associations/relationships in Zephyr and Jira systems.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

zephyr_create_test_execution_issue_link Rate-limited

zephyr_create_test_execution_issue_link 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.

View as policy code

policy.json

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

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

FAQ

Questions about zephyr_create_test_execution_issue_link

What does the zephyr_create_test_execution_issue_link tool do? +

Create a new link between a Jira issue and a Test Execution in Zephyr Examples: 1. Create a link between the test execution with key SA-E40 and the Jira Issue ID 10100 json { "testExecutionIdOrKey": "SA-E40", "issueId": 10100 } Expected Output: The link between Test Execution and Jira issue should be created, but no output is expected. 2. Create a link between the test execution with ID 1 and the Jira Issue ID 20050 json { "testExecutionIdOrKey": "1", "issueId": 20050 } Expected Output: The link between Test Execution and Jira issue should be created, but no output is expected. It is categorised as a Write tool in the SmartBear MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does zephyr_create_test_execution_issue_link accept? +

zephyr_create_test_execution_issue_link accepts 2 parameters: issueId, testExecutionIdOrKey. Required: issueId, testExecutionIdOrKey. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on zephyr_create_test_execution_issue_link? +

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

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

Can I rate-limit zephyr_create_test_execution_issue_link? +

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

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

zephyr_create_test_execution_issue_link 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

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →