qmetry_link_platforms_to_test_suite

// WHEN AI AGENTS USE THIS TOOL

AI agents call qmetry_link_platforms_to_test_suite 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_LINK_PLATFORMS_TO_TEST_SUITE

Even though qmetry_link_platforms_to_test_suite 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_link_platforms_to_test_suite:
    rules:
      - action: allow

See the full SmartBear MCP policy for all 147 tools.

// DETAILS

Tool Name qmetry_link_platforms_to_test_suite

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_link_platforms_to_test_suite tool do? +

Link one or more platforms to a QMetry Test Suite. **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") - qmTsId (number) *required*: Id of Test Suite (required). To get the qmTsId - Call API 'Testsuite/Fetch Testsuite' From the response, get value of following attribute -> data[<index>].id - qmPlatformId (string) *required*: Comma-separated value of PlatformId (required). To get the qmPlatformId - Call API 'Platform/List' From the response, get value of following attribute -> data[<index>].platformID **Output Description:** JSON object with linkage status, success message, and details. **Use Cases:** 1. Link a single platform to a test suite 2. Link multiple platforms to a test suite for cross-platform testing 3. Define execution environments for a test suite 4. Organize test suites by supported platforms 5. Set up platform-specific test suite configurations **Examples:** 1. Link single platform to a test suite ```json { "qmTsId": 1511970, "qmPlatformId": "63004" } ``` Expected Output: Platform 63004 linked to test suite 1511970 successfully. 2. Link multiple platforms to a test suite ```json { "qmTsId": 1511970, "qmPlatformId": "63004,63005,63006" } ``` Expected Output: Platforms 63004, 63005, 63006 linked to test suite 1511970 successfully. **Hints:** 1. CRITICAL: qmTsId and qmPlatformId are REQUIRED parameters 2. To get the qmTsId (Test Suite ID): 3. 1. Call 'Testsuite/Fetch Testsuite' API 4. 2. From response, use data[<index>].id 5. 3. Example: Test Suite 'Login Tests' might have ID 1511970 6. To get the qmPlatformId (Platform ID): 7. 1. Call 'Platform/List' API (Fetch Platforms tool) 8. 2. From response, use data[<index>].platformID 9. 3. Example: Platform 'Chrome' might have ID 63004 10. qmPlatformId accepts comma-separated values for multiple platforms 11. Format for multiple platforms: '63004,63005,63006' 12. No spaces in the comma-separated list 13. If test suite entity key (e.g., VT-TS-12) is provided, first fetch test suites to resolve numeric ID 14. Platforms represent browsers, operating systems, devices, or custom environments 15. This tool helps organize cross-platform test execution 16. Essential for comprehensive platform coverage testing. 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_link_platforms_to_test_suite? +

Add a rule in your Intercept YAML policy under the tools section for qmetry_link_platforms_to_test_suite. 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_link_platforms_to_test_suite? +

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

Can I rate-limit qmetry_link_platforms_to_test_suite? +

Yes. Add a rate_limit block to the qmetry_link_platforms_to_test_suite 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_link_platforms_to_test_suite completely? +

Set action: deny in the Intercept policy for qmetry_link_platforms_to_test_suite. 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_link_platforms_to_test_suite? +

qmetry_link_platforms_to_test_suite 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.

qmetry_link_platforms_to_test_suite

Enforce policies on SmartBear MCP