qmetry_link_issues_to_testcase_run

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") - iss...

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp
Medium RISK CLASS
Category Write
Parameters 42 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/qmetry-link-issues-to-testcase-run.md

What qmetry_link_issues_to_testcase_run does on SmartBear MCP

AI agents use qmetry_link_issues_to_testcase_run 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.

ParameterTypeRequiredDescription
tcrId number Yes ID of Testcase Run to link issues with
baseUrl string The base URL for the QMetry instance (must be a valid URL)
issueIds array Yes ID of issues to be linked to Testcase Run
projectKey string Project key - unique identifier for the project

Parameters from the server's own tool schema.

Why qmetry_link_issues_to_testcase_run is rated Medium

This tool creates associations/links between issues and testcase runs in QMetry. It modifies data by establishing relationships, which is a reversible write operation. It does not delete data, execute code, or involve financial transactions.

From the tool's definition Link one or more issues to a QMetry Testcase Run (execution)

Questions about qmetry_link_issues_to_testcase_run

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 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 qmetry_link_issues_to_testcase_run accept? +

qmetry_link_issues_to_testcase_run accepts 4 parameters: tcrId, baseUrl, issueIds, projectKey. Required: tcrId, issueIds. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on qmetry_link_issues_to_testcase_run? +

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

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

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 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 qmetry_link_issues_to_testcase_run completely? +

Set action: deny in the PolicyLayer 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 server (SmartBear/smartbear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on SmartBear, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of SmartBear's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.