qmetry_link_platforms_to_test_suite

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 42 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/qmetry-link-platforms-to-test-suite.md

WHAT IT DOES

What qmetry_link_platforms_to_test_suite does on SmartBear MCP

AI agents use qmetry_link_platforms_to_test_suite to create or update resources in SmartBear MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SmartBear MCP environment.

Parameter	Type	Required	Description
`qmTsId`	number	Yes	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
`baseUrl`	string	—	The base URL for the QMetry instance (must be a valid URL)
`projectKey`	string	—	Project key - unique identifier for the project
`qmPlatformId`	string	Yes	Comma-separated value of PlatformId (required). To get the qmPlatformId - Call API 'Platform/List' From the response, get value of following attribute -> data[<

Parameters from the server's own tool schema.

RISK

Why qmetry_link_platforms_to_test_suite is rated Medium

This tool creates associations (links) between platforms and a test suite, which is a reversible write operation that modifies existing data relationships rather than deleting anything or executing code.

From the tool's definition Link one or more platforms to a QMetry Test Suite

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs qmetry_link_platforms_to_test_suite 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_link_platforms_to_test_suite, this is the rule to start with:

qmetry_link_platforms_to_test_suite Rate-limited

qmetry_link_platforms_to_test_suite stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "qmetry_link_platforms_to_test_suite": {
      "limits": [
        {
          "counter": "qmetry_link_platforms_to_test_suite_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every qmetry_link_platforms_to_test_suite call is checked against it from then on.

FAQ

Questions about qmetry_link_platforms_to_test_suite

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 Write tool in the SmartBear MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does qmetry_link_platforms_to_test_suite accept? +

qmetry_link_platforms_to_test_suite accepts 4 parameters: qmTsId, baseUrl, projectKey, qmPlatformId. Required: qmTsId, qmPlatformId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on qmetry_link_platforms_to_test_suite? +

Register the SmartBear MCP server in PolicyLayer and add a rule for qmetry_link_platforms_to_test_suite: 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.

What risk level is qmetry_link_platforms_to_test_suite? +

qmetry_link_platforms_to_test_suite is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

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

How do I block qmetry_link_platforms_to_test_suite completely? +

Set action: deny in the PolicyLayer 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 server (SmartBear/smartbear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on SmartBear, and thousands of servers like it.

This server

All 240 SmartBear tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →