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 (st...
Single-target operation
Part of the SmartBear MCP MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call qmetry_link_requirements_to_testcase 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.
Even though qmetry_link_requirements_to_testcase 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.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
qmetry_link_requirements_to_testcase:
rules:
- action: allowSee the full SmartBear MCP policy for all 147 tools.
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 Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for qmetry_link_requirements_to_testcase. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the SmartBear MCP MCP server.
qmetry_link_requirements_to_testcase is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the qmetry_link_requirements_to_testcase 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.
Set action: deny in the Intercept 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.
qmetry_link_requirements_to_testcase 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.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept