qmetry_fetch_requirement_details
Get detailed information for a specific QMetry requirement 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....
This record as markdown: /tools/smartbear-mcp/qmetry-fetch-requirement-details.md
What qmetry_fetch_requirement_details does on SmartBear MCP
AI agents call qmetry_fetch_requirement_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 | Requirement numeric ID (required for fetching specific requirement details). This is the internal numeric identifier, not the entity key like 'MAC-RQ-730'. You |
baseUrl | string | — | The base URL for the QMetry instance (must be a valid URL) |
version | number | Yes | Requirement version number (required for fetching specific requirement version details). 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_requirement_details is rated Low
This tool retrieves requirement details from QMetry by ID lookup. It has no side effects, cannot modify or delete data, and presents no destructive or financial impact. The low severity reflects minimal blast radius if an AI agent queries arbitrary requirement IDs—it can only expose information already accessible within the QMetry instance.
From the tool's definition Tool description states 'Get detailed information for a specific QMetry requirement by numeric ID'. Parameters are all input-only (projectKey, baseUrl, id, version) with no capability to modify, create, or delete data.
Attacks that exploit this kind of access
The rule that runs qmetry_fetch_requirement_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_requirement_details, this is the rule to start with:
qmetry_fetch_requirement_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_requirement_details call is checked against it from then on.
Questions about qmetry_fetch_requirement_details
Get detailed information for a specific QMetry requirement 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*: Requirement numeric ID (required for fetching specific requirement details). This is the internal numeric identifier, not the entity key like 'MAC-RQ-730'. You can get this ID from requirement search results or by using filters. - version (number) *required*: Requirement version number (required for fetching specific requirement version details). This is the internal numeric identifier for the version. Output Description: JSON object with requirement details including ID, key, summary, description, status, and all metadata Use Cases: 1. Get requirement details by numeric ID 2. Retrieve requirement metadata for reporting 3. Get requirement summary and properties 4. Fetch requirement details before linking or updating 5. Access requirement field values and custom fields 6. Get requirement version-specific information Examples: 1. Get requirement details by numeric ID json { "id": 4791316, "version": 1 } Expected Output: Detailed requirement information including summary, description, status, and all fields Hints: 1. This API requires a numeric ID parameter, not entity key 2. If user provides entityKey (e.g., MAC-RQ-730), first call FETCH_REQUIREMENTS with a filter on entityKeyId to resolve the numeric ID 3. After resolving entityKey → numeric ID, call this tool with the resolved numeric ID 4. Version parameter is required - use 1 for the latest version unless user specifies otherwise 5. This tool provides complete requirement information including all custom fields 6. Use this tool to get detailed requirement information that's not available in the list view. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
qmetry_fetch_requirement_details accepts 4 parameters: id, 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_requirement_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_requirement_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_requirement_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_requirement_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_requirement_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