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 ...
Part of the SmartBear MCP MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use zephyr_create_test_execution_issue_link to create or modify resources in SmartBear MCP. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call zephyr_create_test_execution_issue_link repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach SmartBear MCP.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
zephyr_create_test_execution_issue_link:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full SmartBear MCP policy for all 147 tools.
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.
Add a rule in your Intercept YAML policy under the tools section for zephyr_create_test_execution_issue_link. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the SmartBear MCP MCP server.
zephyr_create_test_execution_issue_link is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the zephyr_create_test_execution_issue_link rule in your Intercept 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.
Set action: deny in the Intercept 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.
zephyr_create_test_execution_issue_link is provided by the SmartBear MCP MCP server (@smartbear/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept