qmetry_fetch_platforms

Fetch QMetry platforms 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) - sort (string): Sort criteria as JSON string (default '[{"property":"platformID","direction":"DESC"}]') (default: "[{\"property\":\"platformID\",\"direction\":\"DESC\"}]") - filter (string): Filter criteria as JSON string (default '[]') (default: "[]") Output Description: JSON object with platforms list and pagination metadata Use Cases: 1. Fetch all platforms from the current project 2. Get platform metadata for test execution planning 3. List platforms for test environment selection 4. Filter platforms by name or properties 5. Get paginated platform results for large projects 6. Retrieve platform information for cross-platform testing 7. Search for specific platforms using filters 8. Get platform details for test execution assignment Examples: 1. Get all platforms (default behavior) json {} Expected Output: List of all platforms with default pagination (10 items per page) 2. Get platforms with custom pagination json { "page": 1, "limit": 10, "start": 0 } Expected Output: List of platforms with custom pagination settings 3. Filter platforms by name json { "filter": "[{\"value\":\"Chrome\",\"type\":\"string\",\"field\":\"name\"}]" } Expected Output: Filtered list of platforms matching the name criteria 4. Filter platforms by archive status json { "filter": "[{\"value\":[1,0],\"type\":\"list\",\"field\":\"isArchived\"}]" } Expected Output: List of platforms filtered by archive status (archived and non-archived) 5. Get only archived platforms json { "filter": "[{\"value\":[1],\"type\":\"list\",\"field\":\"isArchived\"}]" } Expected Output: List of only archived platforms 6. Get only active/non-archived platforms json { "filter": "[{\"value\":[0],\"type\":\"list\",\"field\":\"isArchived\"}]" } Expected Output: List of only active/non-archived platforms 7. Get platforms with custom sorting json { "sort": "[{\"property\":\"name\",\"direction\":\"ASC\"}]" } Expected Output: List of platforms sorted by name in ascending order 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. Sort parameter should be a JSON string with sort criteria 5. Default sort: platformID descending 6. Common filter fields: 'name' (string), 'isArchived' (list of 0,1) for archive status 7. IMPORTANT: Always use 'isArchived' field for filtering by archive status, even though response shows 'isPlatformArchived' 8. Archive status values: 0 = active/non-archived, 1 = archived 9. Empty payload {} is sent when no parameters are provided 10. Use platforms for cross-platform testing and environment selection. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.

qmetry_fetch_platforms accepts 7 parameters: page, sort, 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_platforms: 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_platforms 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_platforms 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_platforms. 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_platforms 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.