qmetry_fetch_builds
Fetch QMetry builds from the current project 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") - start (number): Star...
This record as markdown: /tools/smartbear-mcp/qmetry-fetch-builds.md
What qmetry_fetch_builds does on SmartBear MCP
AI agents call qmetry_fetch_builds 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) |
limit | number | — | Number of records (default 10). |
start | number | — | Start index for pagination - defaults to 0 |
filter | string | — | Filter criteria as JSON string (default '[]') |
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.
Why qmetry_fetch_builds is rated Low
This tool retrieves or queries build information from QMetry without any side effects, reversible modifications, code execution, deletion, or financial operations. It is a straightforward read operation with standard pagination and filtering parameters typical of data retrieval APIs.
From the tool's definition Tool name 'qmetry_fetch_builds' and description 'Fetch QMetry builds from the current project' indicate data retrieval. Parameters support querying (projectKey, pagination with start/page/limit, filtering) with no modification or deletion capabilities.
Attacks that exploit this kind of access
The rule that runs qmetry_fetch_builds 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_builds, this is the rule to start with:
qmetry_fetch_builds 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_builds call is checked against it from then on.
Questions about qmetry_fetch_builds
Fetch QMetry builds from the current project 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") - 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) - filter (string): Filter criteria as JSON string (default '[]') (default: "[]") Output Description: JSON object with builds list and pagination metadata Use Cases: 1. Fetch all from the current project 2. Fetch all available builds for test execution planning 3. Get build metadata for test run assignments 4. List builds for reporting and analytics 5. Filter builds by name or archive status 6. Get paginated build results for large projects 7. Retrieve build information for CI/CD integration 8. Search for specific builds using filters 9. Get build details for test execution history Examples: 1. Get all builds (default behavior) json {} Expected Output: List of all builds with default pagination (10 items per page) 2. Get builds with custom pagination json { "page": 1, "limit": 10, "start": 0 } Expected Output: List of builds with custom pagination settings 3. Filter builds by name json { "filter": "[{\"value\":\"Build 1.0\",\"type\":\"string\",\"field\":\"name\"}]" } Expected Output: Filtered list of builds matching the name criteria 4. Filter builds by archive status json { "filter": "[{\"value\":[1,0],\"type\":\"list\",\"field\":\"isArchived\"}]" } Expected Output: List of builds filtered by archive status (archived and non-archived) Hints: 1. Use 'default' project key when user doesn't specify one 2. Default pagination: start=0, page=1, limit=10 3. Filter parameter should be a JSON string with filter criteria 4. Common filter fields: 'name' (string), 'isArchived' (list of 0,1) 5. Empty payload {} is sent when no parameters are provided 6. Builds are also known as 'drops' in QMetry terminology 7. Use builds for associating test executions with specific software versions. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
qmetry_fetch_builds accepts 6 parameters: page, limit, start, filter, baseUrl, projectKey. 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_builds: 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_builds 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_builds 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_builds. 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_builds 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