qmetry_link_test_cases_to_test_suite
Link test cases to a test suite in QMetry. Parameters: - tsID (number) *required*: Id of Test Suite (required) - tcvdIDs (array) *required*: Array of Test Case Version IDs (required if fromReqs is false) - fromReqs (boolean): Link TestCases from Requirements (optional, default false) Output Descr...
This record as markdown: /tools/smartbear-mcp/qmetry-link-test-cases-to-test-suite.md
What qmetry_link_test_cases_to_test_suite does on SmartBear MCP
AI agents use qmetry_link_test_cases_to_test_suite 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 |
|---|---|---|---|
tsID | number | Yes | Id of Test Suite (required) |
tcvdIDs | array | Yes | Array of Test Case Version IDs (required if fromReqs is false) |
fromReqs | boolean | — | Link TestCases from Requirements (optional, default false) |
Parameters from the server's own tool schema.
Why qmetry_link_test_cases_to_test_suite is rated Medium
This tool creates associations/relationships between test cases and a test suite. It modifies data by linking entities together, which is a reversible write operation. It does not delete, execute code, or involve financial transactions.
From the tool's definition Link test cases to a test suite in QMetry
Attacks that exploit this kind of access
The rule that runs qmetry_link_test_cases_to_test_suite 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 qmetry_link_test_cases_to_test_suite, this is the rule to start with:
qmetry_link_test_cases_to_test_suite 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.
The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every qmetry_link_test_cases_to_test_suite call is checked against it from then on.
Questions about qmetry_link_test_cases_to_test_suite
Link test cases to a test suite in QMetry. Parameters: - tsID (number) *required*: Id of Test Suite (required) - tcvdIDs (array) *required*: Array of Test Case Version IDs (required if fromReqs is false) - fromReqs (boolean): Link TestCases from Requirements (optional, default false) Output Description: JSON object with linkage status and details. Use Cases: 1. Link test cases to a test suite by entity keys 2. Bulk link multiple test cases to a suite 3. Automate test suite composition from test cases Examples: 1. Link test cases to a test suite json { "tsID": 8674, "tcvdIDs": [ 5448504, 5448503 ], "fromReqs": false } Expected Output: Test cases QTM-TC-32 and QTM-TC-35 linked to test suite 8674. 2. Link test cases directly to test suites with test cases entityKeys VT-TC-9, VT-TC-10 to test suite id 1487397 json { "tsID": 1487397, "tcvdIDs": [ 5448504, 5448503 ], "fromReqs": false } Expected Output: Test cases VT-TC-9 and VT-TC-10 linked to test suite 1487397. 3. Link test case VT-TC-4, VT-TC-1,VT-TC-101, VT-TC-22 to test suite VT-TS-3 json { "tsID": 1487397, "tcvdIDs": [ 5448504, 5448503, 5448505, 5448506 ], "fromReqs": false } Expected Output: Test cases VT-TC-4, VT-TC-1, VT-TC-101, and VT-TC-22 linked to test suite VT-TS-3. Hints: 1. To get the tsID, call the Fetch Test Suites for Test Case API with rootFolderId otherwise if given folderid so use that and from response get the id. 2. To get the tcvdIDs by testcase entityKey, call the Testcase/Fetch Versions API and use data[<index>].tcVersionID. 3. Set fromReqs to false to direct test case linkage. 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.
qmetry_link_test_cases_to_test_suite accepts 3 parameters: tsID, tcvdIDs, fromReqs. Required: tsID, tcvdIDs. The full parameter table on this page comes from the server's own tool schema.
Register the SmartBear MCP server in PolicyLayer and add a rule for qmetry_link_test_cases_to_test_suite: 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.
qmetry_link_test_cases_to_test_suite 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 qmetry_link_test_cases_to_test_suite 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.
Set action: deny in the PolicyLayer policy for qmetry_link_test_cases_to_test_suite. 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.
qmetry_link_test_cases_to_test_suite 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.
This server
Across the catalogue