qmetry_link_requirements_to_testcase

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 33 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-requirements-to-testcase.md

WHAT IT DOES

What qmetry_link_requirements_to_testcase does on SmartBear MCP

AI agents use qmetry_link_requirements_to_testcase 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
`tcID`	string	Yes	EntityKey of Testcase (e.g. 'COD-TC-29')
`tcVersionId`	number	Yes	Test Case version number. This is the internal numeric identifier for the version.
`rqVersionIds`	string	Yes	Comma-separated values of versionId of the Requirement (e.g. '236124,236125')

Parameters from the server's own tool schema.

RISK

Why qmetry_link_requirements_to_testcase is rated Medium

This tool creates associations (links) between requirements and test cases. It modifies data by establishing relationships in the QMetry system, 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 requirements to a test case by entityKey and version IDs

Attacks that exploit this kind of access

RECOMMENDED RULE

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

qmetry_link_requirements_to_testcase Rate-limited

qmetry_link_requirements_to_testcase 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_link_requirements_to_testcase": {
      "limits": [
        {
          "counter": "qmetry_link_requirements_to_testcase_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_link_requirements_to_testcase call is checked against it from then on.

FAQ

Questions about qmetry_link_requirements_to_testcase

What does the qmetry_link_requirements_to_testcase tool do? +

Link one or more requirements to a test case by entityKey and version IDs. Parameters: - tcID (string) *required*: EntityKey of Testcase (e.g. 'COD-TC-29') - tcVersionId (number) *required*: Test Case version number. This is the internal numeric identifier for the version. - rqVersionIds (string) *required*: Comma-separated values of versionId of the Requirement (e.g. '236124,236125') Output Description: JSON object with success status and linkage details. Use Cases: 1. Link requirements to a test case for traceability 2. Bulk link multiple requirements to a single test case 3. Automate requirement coverage mapping Examples: 1. Link requirements to test case VT-TC-26 json { "tcID": "VT-TC-26", "tcVersionId": 5448515, "rqVersionIds": "5009939,5009937,4970699" } Expected Output: Requirements linked to test case VT-TC-26 successfully. Hints: 1. To get the tcID, call the Testcase/Fetch List for Bulk Operation API and use data[<index>].entityKey. 2. To get the tcVersionId, call the Testcase/Fetch Versions API and use data[<index>].tcVersionID. 3. To get the rqVersionIds, call the requirement/List Versions API and use data[<index>].rqVersionID. 4. If user provides requirement entityKey (e.g., VT-RQ-18), first call requirements list with a filter on entityKeyId to resolve the rqVersionIds 5. If user provides testcase entityKey (e.g., VT-TC-26), first call testcase list with a filter on entityKeyId to resolve the tcVersionId and tcID. 6. rqVersionIds must be a comma-separated string of requirement version 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_requirements_to_testcase accept? +

qmetry_link_requirements_to_testcase accepts 3 parameters: tcID, tcVersionId, rqVersionIds. Required: tcID, tcVersionId, rqVersionIds. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on qmetry_link_requirements_to_testcase? +

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

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

Can I rate-limit qmetry_link_requirements_to_testcase? +

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

Set action: deny in the PolicyLayer policy for qmetry_link_requirements_to_testcase. 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_requirements_to_testcase? +

qmetry_link_requirements_to_testcase 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 →