qmetry_fetch_test_case_details

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Low RISK CLASS

Category Read

Parameters 61 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What qmetry_fetch_test_case_details does on SmartBear MCP

AI agents call qmetry_fetch_test_case_details 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
`baseUrl`	string	—	The base URL for the QMetry instance (must be a valid URL)
`projectKey`	string	—	Project key - unique identifier for the project

Parameters from the server's own tool schema.

RISK

Why qmetry_fetch_test_case_details is rated Low

This tool retrieves test case metadata by ID from a QMetry instance. It performs a read-only query operation with no side effects, data modification, code execution, or destructive capabilities. The blast radius of misuse is limited to information disclosure of test case details.

From the tool's definition Tool name 'qmetry_fetch_test_case_details' and description 'Get detailed information for a specific QMetry test case' indicates data retrieval. Parameters are all for lookup (projectKey, tcID, baseUrl, start pagination) with no modification capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

qmetry_fetch_test_case_details Allowed

qmetry_fetch_test_case_details 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_test_case_details": {}
  }
}

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

FAQ

Questions about qmetry_fetch_test_case_details

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.

What parameters does qmetry_fetch_test_case_details accept? +

qmetry_fetch_test_case_details accepts 6 parameters: page, tcID, limit, start, baseUrl, 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_test_case_details? +

Register the SmartBear MCP server in PolicyLayer and add a rule for qmetry_fetch_test_case_details: 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_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 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_test_case_details completely? +

Set action: deny in the PolicyLayer 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 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

get_event_details on CTFtime MCP Server → The MCP Attack Database →

Guides

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