qmetry_fetch_issues_linked_to_test_case

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Low RISK CLASS

Category Read

Parameters 81 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What qmetry_fetch_issues_linked_to_test_case does on SmartBear MCP

AI agents call qmetry_fetch_issues_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 those issues that are linked with this Test case Run, False to get those issues which are not linked with this Test case Run. Default value tru
`projectKey`	string	—	Project key - unique identifier for the project

Parameters from the server's own tool schema.

RISK

Why qmetry_fetch_issues_linked_to_test_case is rated Low

This tool retrieves and queries existing data from QMetry without modifying, deleting, or executing operations. It is a straightforward data retrieval operation that returns linked issues for a given test case, presenting no side effects or risk of data modification.

From the tool's definition Tool name contains 'fetch'; description states 'Get issues that are linked...to a specific test case'; parameters are all read-only queries (projectKey, baseUrl, tcID, getLinked) with no mutation or deletion capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

qmetry_fetch_issues_linked_to_test_case Allowed

qmetry_fetch_issues_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_issues_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_issues_linked_to_test_case call is checked against it from then on.

FAQ

Questions about qmetry_fetch_issues_linked_to_test_case

What does the qmetry_fetch_issues_linked_to_test_case tool do? +

Get issues 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 those issues that are linked with this Test case Run, False to get those issues which are not linked with this Test case Run. Default value true (get linked issues). (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) - filter (string): Filter criteria as JSON string (default '[]') (default: "[]") Output Description: JSON object with issues array containing issue details, priorities, status, and linkage information Use Cases: 1. Get all issues linked to a specific test case for defect tracking 2. Find issues that are NOT linked to a test case (gap analysis) 3. Generate traceability reports between test cases and issues 4. Filter issues by type, priority, status, or owner 5. Monitor issue resolution progress for specific test cases 6. Audit issue-test case relationships for compliance 7. Filter issues by summary content or execution version 8. Get issue details for test execution planning 9. Track linkage level (Test Case vs Test Step level) 10. Quality assurance - ensure proper issue tracking Examples: 1. Get all issues linked to test case ID 4495658 (default behavior) json { "tcID": 4495658 } Expected Output: List of issues linked to the test case with issue details, status, and metadata 2. Get all issues linked to test case ID 4495658 (explicit) json { "tcID": 4495658, "getLinked": true } Expected Output: List of issues linked to the test case with issue details, status, and metadata 3. Get issues NOT linked to test case (gap analysis) json { "tcID": 4495658, "getLinked": false } Expected Output: List of issues that are NOT linked to the test case 4. Get linked issues with pagination json { "tcID": 4495658, "getLinked": true, "limit": 25, "page": 1 } Expected Output: Paginated list of issues linked to the test case 5. Filter linked issues by summary content (using default getLinked=true) json { "tcID": 4495658, "filter": "[{\"value\":\"login\",\"type\":\"string\",\"field\":\"summary\"}]" } Expected Output: Issues linked to test case that contain 'login' in their summary 6. Filter linked issues by status and priority json { "tcID": 4495658, "getLinked": true, "filter": "[{\"value\":[1,2],\"type\":\"list\",\"field\":\"issueState\"},{\"value\":[1],\"type\":\"list\",\"field\":\"issuePriority\"}]" } Expected Output: High priority issues in Open or In Progress status 7. Filter issues by execution version json { "tcID": 4495658, "getLinked": true, "filter": "[{\"value\":\"2\",\"type\":\"string\",\"field\":\"executedVersion\"}]" } Expected Output: Issues linked to version 2 of the test case execution Hints: 1. CRITICAL: tcID parameter is REQUIRED - this is the Test Case numeric ID 2. getLinked parameter is OPTIONAL - defaults to true if not provided 3. HOW TO GET tcID: 4. 1. Call FETCH_TEST_CASES with filter on entityKeyId to resolve test case key to numeric ID 5. 2. From response, use data[index].tcID field 6. 3. Example: MAC-TC-1684 → tcID: 4495658 7. getLinked=true (default): Returns issues that ARE linked to the test case 8. getLinked=false: Returns issues that are NOT linked to the test case (useful for gap analysis) 9. If getLinked is not specified, it defaults to true (linked issues) 10. FILTER CAPABILITIES: Extensive filtering by issue properties 11. FILTER FIELDS: summary (string), executedVersion (string), linkageLevel (string), issueType (list), issuePriority (list), issueState (list), owner (list) 12. LINKAGE LEVEL: 'Test Case' for test case level links, 'Test Step' for step level links 13. ISSUE TYPE IDs: Typically 1=Bug, 2=Enhancement, 3=Task (verify with your QMetry instance) 14. ISSUE PRIORITY IDs: Typically 1=High, 2=Medium, 3=Low (verify with your QMetry instance) 15. ISSUE STATUS IDs: Typically 1=Open, 2=In Progress, 3=Resolved, 4=Closed (verify with your QMetry instance) 16. OWNER IDs: Use numeric user IDs from QMetry user management 17. Multiple filter conditions are combined with AND logic 18. Use pagination for large issue result sets (start, page, limit parameters) 19. This tool is essential for defect tracking and traceability audits 20. Helps establish relationships between test failures and reported issues 21. Critical for impact analysis when test cases change 22. Use for compliance reporting and quality metrics. 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_issues_linked_to_test_case accept? +

qmetry_fetch_issues_linked_to_test_case accepts 8 parameters: page, tcID, limit, start, filter, baseUrl, getLinked, projectKey. 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_issues_linked_to_test_case? +

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

qmetry_fetch_issues_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_issues_linked_to_test_case? +

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

Set action: deny in the PolicyLayer policy for qmetry_fetch_issues_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_issues_linked_to_test_case? +

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