qmetry_requirements_linked_test_cases_to_test_suite

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 32 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/qmetry-requirements-linked-test-cases-to-test-suite.md

WHAT IT DOES

What qmetry_requirements_linked_test_cases_to_test_suite does on SmartBear MCP

AI agents use qmetry_requirements_linked_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 true)
`fromReqs`	boolean	—	Link TestCases from Requirements (optional, default true)

Parameters from the server's own tool schema.

RISK

Why qmetry_requirements_linked_test_cases_to_test_suite is rated Medium

This tool creates associations between test cases and a test suite. It modifies data by establishing linkages, which is a reversible write operation. It does not delete or execute code, and has moderate blast radius as misuse could result in incorrect test suite compositions.

From the tool's definition Link test cases (including those linked to requirements) to a test suite in QMetry

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs qmetry_requirements_linked_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_requirements_linked_test_cases_to_test_suite, this is the rule to start with:

qmetry_requirements_linked_test_cases_to_test_suite Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "qmetry_requirements_linked_test_cases_to_test_suite": {
      "limits": [
        {
          "counter": "qmetry_requirements_linked_test_cases_to_test_suite_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every qmetry_requirements_linked_test_cases_to_test_suite call is checked against it from then on.

FAQ

Questions about qmetry_requirements_linked_test_cases_to_test_suite

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

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

How do I enforce a policy on qmetry_requirements_linked_test_cases_to_test_suite? +

Register the SmartBear MCP server in PolicyLayer and add a rule for qmetry_requirements_linked_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.

What risk level is qmetry_requirements_linked_test_cases_to_test_suite? +

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

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

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

KEEP EXPLORING

More on SmartBear, and thousands of servers like it.

This server

All 240 SmartBear tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →