qmetry_requirements_linked_test_cases_to_test_suite

// WHEN AI AGENTS USE THIS TOOL

AI agents call qmetry_requirements_linked_test_cases_to_test_suite to retrieve information from SmartBear MCP without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON QMETRY_REQUIREMENTS_LINKED_TEST_CASES_TO_TEST_SUITE

Even though qmetry_requirements_linked_test_cases_to_test_suite only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

smartbear-mcp.yaml

tools:
  qmetry_requirements_linked_test_cases_to_test_suite:
    rules:
      - action: allow

See the full SmartBear MCP policy for all 147 tools.

// DETAILS

Tool Name qmetry_requirements_linked_test_cases_to_test_suite

Category Read

MCP Server SmartBear MCP MCP Server

Risk Level Low

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

View all 147 tools →

// RELATED READING

// FAQ

What does the qmetry_requirements_linked_test_cases_to_test_suite tool do? +

Link test cases (including those linked to requirements) 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 true) - fromReqs (boolean): Link TestCases from Requirements (optional, default true) **Output Description:** JSON object with linkage status and details. **Use Cases:** 1. Link requirements linked test cases to a test suite 2. Bulk link multiple requirements linked test cases to a suite 3. Automate test suite composition from requirements linked test cases **Examples:** 1. VT-RQ-18 Requirements Linked test cases to a test suite ```json { "tsID": 8674, "tcvdIDs": [ 5448504, 5448503 ], "fromReqs": true } ``` Expected Output: Test cases QTM-TC-32 and QTM-TC-35 linked to test suite 8674. 2. VT-RQ-19 Requirements Linked test cases to test suites id 1487397 ```json { "tsID": 1487397, "tcvdIDs": [ 5448504, 5448503 ], "fromReqs": true } ``` Expected Output: Test cases VT-TC-9 and VT-TC-10 linked to test suite 1487397. 3. VT-RQ-20 Requirements Linked test case to test suite VT-TS-3 ```json { "tsID": 1487397, "tcvdIDs": [ 5448504, 5448503, 5448505, 5448506 ], "fromReqs": true } ``` 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 requirement linked tcvdIDs by requirement entityKey, call the Fetch Test Cases Linked to Requirement API by <requirementEntityKey> to fetch If user provides entityKey (e.g., MAC-RQ-1011), first call FETCH_REQUIREMENTS with filter on entityKeyId to resolve the numeric rqID and get the linked test cases version ids. 3. Set fromReqs to true to link requirements linked test cases instead of direct test case linkage.. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on qmetry_requirements_linked_test_cases_to_test_suite? +

Add a rule in your Intercept YAML policy under the tools section for qmetry_requirements_linked_test_cases_to_test_suite. 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_requirements_linked_test_cases_to_test_suite? +

qmetry_requirements_linked_test_cases_to_test_suite is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit qmetry_requirements_linked_test_cases_to_test_suite? +

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

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

What MCP server provides qmetry_requirements_linked_test_cases_to_test_suite? +

qmetry_requirements_linked_test_cases_to_test_suite 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_requirements_linked_test_cases_to_test_suite

Enforce policies on SmartBear MCP