qmetry_fetch_test_case_details

// WHEN AI AGENTS USE THIS TOOL

AI agents call qmetry_fetch_test_case_details 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.

// WHY ENFORCE A POLICY ON QMETRY_FETCH_TEST_CASE_DETAILS

Even though qmetry_fetch_test_case_details 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.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

smartbear-mcp.yaml

tools:
  qmetry_fetch_test_case_details:
    rules:
      - action: allow

See the full SmartBear MCP policy for all 147 tools.

// DETAILS

Tool Name qmetry_fetch_test_case_details

Category Read

MCP Server SmartBear MCP MCP Server

Risk Level Low

// MORE SMARTBEAR MCP TOOLS

Destructive collaborator_delete_collaborator_remote_system_configuration Destructive reflect_cancel_suite_execution Destructive reflect_delete_previous_step Destructive swagger_delete_portal_product Destructive swagger_delete_table_of_contents Execute collaborator_reviewservice_action Execute contract-testing_can_i_deploy Execute qmetry_link_issues_to_testcase_run

View all 147 tools →

// RELATED READING

// FAQ

What does the qmetry_fetch_test_case_details tool do? +

Get detailed information for a specific QMetry test case by numeric ID - USE THIS for single test case lookup **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. - 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) **Output Description:** JSON object with test case details including ID, key, summary, description, and metadata **Use Cases:** 1. Get test case details by numeric ID (PREFERRED for single test case) 2. Fetch test case when user provides entityKey (e.g., 'VKMCP-TC-5') 3. Retrieve test case metadata for a specific test case 4. Get test case summary and properties for display or editing 5. Fetch test case details before accessing steps or version details 6. Lookup test case by name or ID without affecting UI filters **Examples:** 1. Get test case details by numeric ID ```json { "tcID": 4468020 } ``` Expected Output: Detailed test case information including summary, description, status **Hints:** 1. USE THIS TOOL when user asks to 'fetch test case VKMCP-TC-5' or 'get test case by ID' or 'find test case X' 2. This API requires a numeric tcID parameter 3. CRITICAL: If user provides entityKey (e.g., MAC-TC-1684), you have TWO options: 4. Option 1 (RECOMMENDED): Ask user for the numeric test case ID 5. Option 2: If you must resolve entityKey, use FETCH_TEST_CASES with filter ONLY ONCE, then immediately use this tool 6. After resolving entityKey → tcID, always use THIS tool (FETCH_TEST_CASE_DETAILS) for subsequent lookups 7. This tool provides metadata and properties; use FETCH_TEST_CASE_STEPS for step-level details 8. This tool does NOT persist filters in UI - safe for single test case lookups 9. ALWAYS prefer this tool over FETCH_TEST_CASES with filters for single test case operations. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on qmetry_fetch_test_case_details? +

Add a rule in your Intercept YAML policy under the tools section for qmetry_fetch_test_case_details. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the SmartBear MCP MCP server.

What risk level is qmetry_fetch_test_case_details? +

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

Can I rate-limit qmetry_fetch_test_case_details? +

Yes. Add a rate_limit block to the qmetry_fetch_test_case_details 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.

How do I block qmetry_fetch_test_case_details completely? +

Set action: deny in the Intercept policy for qmetry_fetch_test_case_details. 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_test_case_details? +

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

Enforce policies on SmartBear MCP