qmetry_fetch_test_case_version_details
Get QMetry test case details for a specific version by numeric ID 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") -...
This record as markdown: /tools/smartbear-mcp/qmetry-fetch-test-case-version-details.md
What qmetry_fetch_test_case_version_details does on SmartBear MCP
AI agents call qmetry_fetch_test_case_version_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 |
|---|---|---|---|
id | number | Yes | Test Case numeric ID (required for fetching steps or version details). This is the internal numeric identifier, not the entity key like 'MAC-TC-1684'. You can g |
scope | string | — | Scope of the operation - defines the context for data retrieval. Common values: 'project' (default), 'folder', 'release', 'cycle'. Applies to any entity type be |
baseUrl | string | — | The base URL for the QMetry instance (must be a valid URL) |
version | number | Yes | Test Case version number. This is the internal numeric identifier for the version. |
projectKey | string | — | Project key - unique identifier for the project |
Parameters from the server's own tool schema.
Why qmetry_fetch_test_case_version_details is rated Low
This tool retrieves and queries test case version details from QMetry without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval function with no side effects, making it a Read category tool with low severity risk.
From the tool's definition Tool name contains 'fetch' and description states 'Get QMetry test case details' with parameters for querying by ID and version. No modification, deletion, or execution capabilities described.
Attacks that exploit this kind of access
The rule that runs qmetry_fetch_test_case_version_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_version_details, this is the rule to start with:
qmetry_fetch_test_case_version_details is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every qmetry_fetch_test_case_version_details call is checked against it from then on.
Questions about qmetry_fetch_test_case_version_details
Get QMetry test case details for a specific version by numeric ID 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") - id (number) *required*: Test Case numeric ID (required for fetching steps or version details). This is the internal numeric identifier, not the entity key like 'MAC-TC-1684'. You can get this ID from test case search results. - version (number) *required*: Test Case version number. This is the internal numeric identifier for the version. - scope (string): Scope of the operation - defines the context for data retrieval. Common values: 'project' (default), 'folder', 'release', 'cycle'. Applies to any entity type being fetched or operated upon. (default: "project") Output Description: JSON object with version-specific test case details Use Cases: 1. Get specific version details of a test case 2. Compare different versions of a test case 3. Retrieve version history information 4. Audit changes made across test case versions Examples: 1. Get version 2 details for test case ID 123 json { "id": 123, "version": 2 } Expected Output: Version 2 details for test case 123 Hints: 1. Requires numeric ID, not entityKey 2. If user provides entityKey (e.g., MAC-TC-1684), first resolve it to numeric ID using FETCH_TEST_CASES 3. Version defaults to 1 if not specified 4. Provides version-specific metadata and history. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
qmetry_fetch_test_case_version_details accepts 5 parameters: id, scope, baseUrl, version, projectKey. Required: id, version. The full parameter table on this page comes from the server's own tool schema.
Register the SmartBear MCP server in PolicyLayer and add a rule for qmetry_fetch_test_case_version_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.
qmetry_fetch_test_case_version_details 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_fetch_test_case_version_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.
Set action: deny in the PolicyLayer policy for qmetry_fetch_test_case_version_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.
qmetry_fetch_test_case_version_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.
More on SmartBear, and thousands of servers like it.
This server
Across the catalogue