qmetry_link_issues_to_testcase_run

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke qmetry_link_issues_to_testcase_run to trigger processes or run actions in SmartBear MCP. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

// WHY ENFORCE A POLICY ON QMETRY_LINK_ISSUES_TO_TESTCASE_RUN

qmetry_link_issues_to_testcase_run can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

smartbear-mcp.yaml

tools:
  qmetry_link_issues_to_testcase_run:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full SmartBear MCP policy for all 147 tools.

// DETAILS

Tool Name qmetry_link_issues_to_testcase_run

Category Execute

MCP Server SmartBear MCP MCP Server

Risk Level High

// MORE SMARTBEAR MCP TOOLS

Destructive collaborator_delete_collaborator_remote_system_configuration Destructive reflect_cancel_suite_execution Destructive reflect_delete_previous_step Destructive swagger_delete_portal_product Destructive swagger_delete_table_of_contents Execute collaborator_reviewservice_action Execute contract-testing_can_i_deploy Execute reflect_execute_suite

View all 147 tools →

// RELATED READING

// FAQ

What does the qmetry_link_issues_to_testcase_run tool do? +

Link one or more issues to a QMetry Testcase Run (execution). **Parameters:** - projectKey (string): Project key - unique identifier for the project (default: "default") - baseUrl (string): The base URL for the QMetry instance (must be a valid URL) (default: "https://testmanagement.qmetry.com") - issueIds (array) *required*: ID of issues to be linked to Testcase Run - tcrId (number) *required*: ID of Testcase Run to link issues with **Output Description:** JSON object with linkage status and details. **Use Cases:** 1. Link a single issue to a testcase run 2. Link multiple issues to a testcase run 3. Automate defect association during test execution 4. Maintain traceability between defects and test runs **Examples:** 1. Link one issue to a testcase run ```json { "issueIds": [ "5054834" ], "tcrId": 567890 } ``` Expected Output: Issue 5054834 linked to testcase run 567890 successfully. 2. Link multiple issues to a testcase run ```json { "issueIds": [ "5054834", "5054835" ], "tcrId": 567890 } ``` Expected Output: Issues 5054834, 5054835 linked to testcase run 567890 successfully. **Hints:** 1. if you have pass issue key (VT-IS-5, MAC-IS-10 etc.) then first fetch issue by issue key to get issue id. 2. To get the issueIds, call the Fetch issues linked with testcases tool and use data[<index>].defectID from the response. 3. To get the tcrId, call the Execution/Fetch Testcase Run ID tool and use data[<index>].tcRunID from the response. 4. Both issueIds and tcrId are required. 5. You can link multiple issues at once by providing an array of IDs.. It is categorised as a Execute tool in the SmartBear MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on qmetry_link_issues_to_testcase_run? +

Add a rule in your Intercept YAML policy under the tools section for qmetry_link_issues_to_testcase_run. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the SmartBear MCP MCP server.

What risk level is qmetry_link_issues_to_testcase_run? +

qmetry_link_issues_to_testcase_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit qmetry_link_issues_to_testcase_run? +

Yes. Add a rate_limit block to the qmetry_link_issues_to_testcase_run 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.

How do I block qmetry_link_issues_to_testcase_run completely? +

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

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

qmetry_link_issues_to_testcase_run

Enforce policies on SmartBear MCP