qmetry_fetch_test_case_steps
Get detailed test case steps for a specific test case 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-steps.md
What qmetry_fetch_test_case_steps does on SmartBear MCP
AI agents call qmetry_fetch_test_case_steps 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 |
page | number | — | Page number to return (starts from 1) |
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) |
version | number | — | Test Case version number (optional, defaults to 1). 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_steps is rated Low
This tool queries and retrieves test case information from QMetry by ID and version. It performs a GET-like operation with no capability to modify, delete, or execute code. The blast radius of misuse is minimal — an attacker could only read test case details they have access to query. Classified as Read with low severity.
From the tool's definition Tool description states 'Get detailed test case steps for a specific test case' — a retrieval operation. Parameters are all read-only inputs (projectKey, baseUrl, id, version) with no write, delete, or execute capabilities.
Attacks that exploit this kind of access
The rule that runs qmetry_fetch_test_case_steps 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_steps, this is the rule to start with:
qmetry_fetch_test_case_steps 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_steps call is checked against it from then on.
Questions about qmetry_fetch_test_case_steps
Get detailed test case steps for a specific test case 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): Test Case version number (optional, defaults to 1). This is the internal numeric identifier for the version. - 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 array of test steps including step description, expected result, and order Use Cases: 1. Get step-by-step instructions with expected results 2. Retrieve test case execution procedure for manual runs 3. Export or display detailed test steps for documentation 4. Fetch steps before automation mapping Examples: 1. Get steps for test case ID 123 json { "id": 123 } Expected Output: Detailed steps with actions and expected results for test case 123 Hints: 1. Requires numeric ID, not entityKey 2. If user provides entityKey (e.g., MAC-TC-1684), resolve it first via FETCH_TEST_CASES to get the numeric ID 3. Version defaults to 1 if not specified 4. Use pagination for test cases with many steps. 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_steps accepts 7 parameters: id, page, limit, start, baseUrl, version, projectKey. Required: id. 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_steps: 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_steps 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_steps 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_steps. 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_steps 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