qmetry_fetch_requirements_linked_to_test_case

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Low RISK CLASS

Category Read

Parameters 91 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What qmetry_fetch_requirements_linked_to_test_case does on SmartBear MCP

AI agents call qmetry_fetch_requirements_linked_to_test_case to retrieve information from SmartBear MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`page`	number	—	Page number to return (starts from 1)
`tcID`	number	Yes	Test Case numeric ID. This is the internal numeric identifier, not the entity key like 'MAC-TC-1684'. You can get this ID from test case search results or by us
`limit`	number	—	Number of records (default 10).
`start`	number	—	Start index for pagination - defaults to 0
`filter`	string	—	Filter criteria as JSON string (default '[]')
`baseUrl`	string	—	The base URL for the QMetry instance (must be a valid URL)
`getLinked`	boolean	—	True to get only requirements that are linked with this test case, false to get requirements which are not linked with this test case. Defaults to true (get lin
`projectKey`	string	—	Project key - unique identifier for the project
`rqFolderPath`	string	—	Folder path for requirements - SYSTEM AUTOMATICALLY SETS TO ROOT. Leave empty unless you want specific folder. System will automatically use empty string "" (ro

Parameters from the server's own tool schema.

RISK

Why qmetry_fetch_requirements_linked_to_test_case is rated Low

This tool retrieves and queries data from a test management system without creating, modifying, or deleting any resources. It is a straightforward Read operation with minimal blast radius if misused by an AI agent — the worst outcome would be unauthorized information disclosure about test requirements, which is typical low-severity Read access.

From the tool's definition Tool description states 'Get requirements that are linked (or not linked) to a specific test case' — purely a retrieval operation with no modifications, deletions, or side effects.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

qmetry_fetch_requirements_linked_to_test_case Allowed

qmetry_fetch_requirements_linked_to_test_case is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "qmetry_fetch_requirements_linked_to_test_case": {}
  }
}

ALLOW ONLY 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_fetch_requirements_linked_to_test_case call is checked against it from then on.

FAQ

Questions about qmetry_fetch_requirements_linked_to_test_case

What does the qmetry_fetch_requirements_linked_to_test_case tool do? +

Get requirements that are linked (or not linked) to a specific test case in QMetry Parameters: - projectKey (string): Project key - unique identifier for the project (default: "default") - baseUrl (string): The base URL for the QMetry instance (must be a valid URL) (default: "https://testmanagement.qmetry.com") - tcID (number) *required*: Test Case numeric ID. This is the internal numeric identifier, not the entity key like 'MAC-TC-1684'. You can get this ID from test case search results or by using filters. - getLinked (boolean): True to get only requirements that are linked with this test case, false to get requirements which are not linked with this test case. Defaults to true (get linked requirements). (default: true) - start (number): Start index for pagination - defaults to 0 (default: 0) - page (number): Page number to return (starts from 1) (default: 1) - limit (number): Number of records (default 10). (default: 10) - rqFolderPath (string): Folder path for requirements - SYSTEM AUTOMATICALLY SETS TO ROOT. Leave empty unless you want specific folder. System will automatically use empty string "" (root directory). Only specify if user wants specific folder like "Automation/Regression". (default: "") - filter (string): Filter criteria as JSON string (default '[]') (default: "[]") Output Description: JSON object with requirements array, traceability information, and pagination metadata Use Cases: 1. Get all requirements linked to a specific test case for traceability analysis 2. Find requirements that are NOT linked to a test case (gap analysis) 3. Verify test case coverage by checking linked requirements 4. Impact analysis - see which requirements are affected when a test case changes 5. Generate traceability matrix between test cases and requirements 6. Filter linked requirements by various criteria 7. Audit test case-requirement relationships for compliance 8. Identify orphaned requirements or test cases without proper links 9. Plan requirement validation based on test case-requirement associations 10. Quality assurance - ensure all test cases have proper requirement coverage Examples: 1. Get all requirements linked to test case ID 594294 json { "tcID": 594294 } Expected Output: List of requirements that are linked to test case MAC-TC-1684 2. Get requirements NOT linked to test case (gap analysis) json { "tcID": 594294, "getLinked": false } Expected Output: List of requirements that are NOT linked to test case MAC-TC-1684 3. Get linked requirements from specific folder json { "tcID": 594294, "rqFolderPath": "/CodeSnippets" } Expected Output: Linked requirements located in the '/CodeSnippets' folder 4. Search linked requirements by entity key json { "tcID": 594294, "filter": "[{\"type\":\"string\",\"value\":\"MAC-RQ-730,MAC-RQ-731\",\"field\":\"entityKeyId\"}]" } Expected Output: Linked requirements matching specific entity keys 5. Filter linked requirements by status json { "tcID": 594294, "filter": "[{\"type\":\"list\",\"value\":[1,2],\"field\":\"requirementStateAlias\"}]" } Expected Output: Linked requirements with Open or Approved status 6. Filter linked requirements by priority json { "tcID": 594294, "filter": "[{\"type\":\"list\",\"value\":[1],\"field\":\"priorityAlias\"}]" } Expected Output: Linked requirements with High priority 7. Filter linked requirements by archive status json { "tcID": 594294, "filter": "[{\"type\":\"list\",\"value\":[0],\"field\":\"isArchived\"}]" } Expected Output: Active (non-archived) linked requirements 8. Search linked requirements by name content json { "tcID": 594294, "filter": "[{\"type\":\"string\",\"value\":\"authentication\",\"field\":\"name\"}]" } Expected Output: Linked requirements with 'authentication' in their name 9. Filter linked requirements by test case version json { "tcID": 594294, "filter": "[{\"type\":\"string\",\"value\":\"1\",\"field\":\"tcVersion\"}]" } Expected Output: Requirements linked to version 1 of the test case 10. Filter linked requirements by release and cycle json { "tcID": 594294, "filter": "[{\"type\":\"list\",\"value\":[55178],\"field\":\"release\"},{\"type\":\"list\",\"value\":[111577],\"field\":\"cycle\"}]" } Expected Output: Linked requirements in Release 8.12 and Cycle 8.12.1 Hints: 1. This API requires a numeric tcID parameter, not entity key 2. If user provides entityKey (e.g., MAC-TC-1684), first call FETCH_TEST_CASES with filter on entityKeyId to resolve the numeric tcID 3. After resolving entityKey → tcID, call this tool with the resolved numeric tcID 4. TRACEABILITY WORKFLOW: Use this tool to establish test case-requirement traceability matrix 5. getLinked=true (default): Returns requirements that ARE linked to the test case 6. getLinked=false: Returns requirements that are NOT linked to the test case (useful for gap analysis) 7. rqFolderPath: Use empty string '' for root folder or specific path like '/CodeSnippets' 8. FILTER CAPABILITIES: Support same filters as regular requirement listing 9. FILTER FIELDS: name, entityKeyId, requirementStateAlias, priorityAlias, createdByAlias, tcVersion, release, cycle, isArchived, componentAlias 10. Multiple filter conditions are combined with AND logic 11. For entity key search, use comma-separated values: 'MAC-RQ-1,MAC-RQ-2,MAC-RQ-3' 12. This tool is crucial for compliance, traceability audits, and impact analysis 13. Pagination supported for large result sets (start, page, limit parameters) 14. Use this tool to verify that test cases properly cover requirements 15. Essential for requirement validation and test case completeness analysis. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.

What parameters does qmetry_fetch_requirements_linked_to_test_case accept? +

qmetry_fetch_requirements_linked_to_test_case accepts 9 parameters: page, tcID, limit, start, filter, baseUrl, getLinked, projectKey, rqFolderPath. Required: tcID. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on qmetry_fetch_requirements_linked_to_test_case? +

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

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

Can I rate-limit qmetry_fetch_requirements_linked_to_test_case? +

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

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

qmetry_fetch_requirements_linked_to_test_case 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

Roll out MCP under one policy →Data exfiltration →MCP token cost →