qmetry_fetch_platforms

// WHEN AI AGENTS USE THIS TOOL

AI agents call qmetry_fetch_platforms to retrieve information from SmartBear MCP without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON QMETRY_FETCH_PLATFORMS

Even though qmetry_fetch_platforms only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

smartbear-mcp.yaml

tools:
  qmetry_fetch_platforms:
    rules:
      - action: allow

See the full SmartBear MCP policy for all 147 tools.

// DETAILS

Tool Name qmetry_fetch_platforms

Category Read

MCP Server SmartBear MCP MCP Server

Risk Level Low

// MORE SMARTBEAR MCP TOOLS

Destructive collaborator_delete_collaborator_remote_system_configuration Destructive reflect_cancel_suite_execution Destructive reflect_delete_previous_step Destructive swagger_delete_portal_product Destructive swagger_delete_table_of_contents Execute collaborator_reviewservice_action Execute contract-testing_can_i_deploy Execute qmetry_link_issues_to_testcase_run

View all 147 tools →

// RELATED READING

// FAQ

What does the qmetry_fetch_platforms tool do? +

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.

How do I enforce a policy on qmetry_fetch_platforms? +

Add a rule in your Intercept YAML policy under the tools section for qmetry_fetch_platforms. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the SmartBear MCP MCP server.

What risk level is qmetry_fetch_platforms? +

qmetry_fetch_platforms is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit qmetry_fetch_platforms? +

Yes. Add a rate_limit block to the qmetry_fetch_platforms rule in your Intercept 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.

How do I block qmetry_fetch_platforms completely? +

Set action: deny in the Intercept 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.

What MCP server provides qmetry_fetch_platforms? +

qmetry_fetch_platforms is provided by the SmartBear MCP MCP server (@smartbear/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on SmartBear MCP