qmetry_update_test_suite

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 73 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/qmetry-update-test-suite.md

WHAT IT DOES

What qmetry_update_test_suite does on SmartBear MCP

AI agents use qmetry_update_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
`id`	number	Yes	Id of Test Suite to be updated (required)
`name`	string	—	Name of the Test Suite
`entityKey`	string	Yes	Entity Key of Test Suite to be updated (required)
`TsFolderID`	number	Yes	Folder ID where Test Suite resides (required)
`description`	string	—	Description of the Test Suite
`testSuiteState`	number	—	State of the Test Suite
`testsuiteOwner`	number	—	Owner ID of the Test Suite

Parameters from the server's own tool schema.

RISK

Why qmetry_update_test_suite is rated Medium

This tool creates or modifies data reversibly by updating an existing test suite's properties (name, description, owner, state). It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or trigger external operations with unpredictable effects.

From the tool's definition Tool name 'qmetry_update_test_suite' and description 'Update an existing QMetry test suite' indicates modification of data. Parameters include id, name, description, testsuiteOwner, and testSuiteState which are all updatable fields.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

qmetry_update_test_suite Rate-limited

qmetry_update_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_update_test_suite": {
      "limits": [
        {
          "counter": "qmetry_update_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_update_test_suite call is checked against it from then on.

FAQ

Questions about qmetry_update_test_suite

What does the qmetry_update_test_suite tool do? +

Update an existing QMetry test suite by id(testsuite numeric id), with auto-resolution from entityKey. Parameters: - id (number) *required*: Id of Test Suite to be updated (required) - TsFolderID (number) *required*: Folder ID where Test Suite resides (required) - entityKey (string) *required*: Entity Key of Test Suite to be updated (required) - name (string): Name of the Test Suite - description (string): Description of the Test Suite - testsuiteOwner (number): Owner ID of the Test Suite - testSuiteState (number): State of the Test Suite Output Description: JSON object containing the new test suite ID, summary, and creation metadata. Use Cases: 1. Update test suite summary (name) 2. Change owner, or state of a test suite 3. Bulk update using entityKey auto-resolution 4. Modify test suite description Examples: 1. Update test suite summary (updated name) json { "id": 1505898, "entityKey": "VT-TS-7", "TsFolderID": 1644087, "name": "MAC Test11" } Expected Output: Test suite summary updated. Only 'name' field changed. Field IDs auto-resolved from project info. id(test suite numeric id) resolved from entityKey. TsFolderID auto-resolved. from the project info. info on rootFolders.TS.id. 2. Update state to Open and owner of the test suite json { "id": 1505898, "entityKey": "VT-TS-7", "TsFolderID": 1644087, "testSuiteState": 505036, "testsuiteOwner": 6963 } Expected Output: State and owner updated. Example uses: testSuiteState=505036 (Open from customListObjs.testSuiteState[index].id), testsuiteOwner=6963 (umang.savaliya from customListObjs.owner[index].id). Field IDs auto-resolved from project info. id(test suite numeric id) resolved from entityKey. TsFolderID auto-resolved from the project info rootFolders.TS.id. 3. Update only description of the test suite json { "id": 1505898, "entityKey": "VT-TS-7", "TsFolderID": 1644087, "description": "Updated description for the test suite." } Expected Output: description updated only. Field IDs auto-resolved from project info. id(test suite numeric id) resolved from entityKey. TsFolderID auto-resolved. from the project info. info on rootFolders.TS.id. Hints: 1. If user provides entityKey (e.g., MAC-TS-7), first call Fetch Test Suites with a filter on entityKeyId to resolve the id (test suite numeric id) and TsFolderID from rootFolders.TS.id. 2. To get valid values for owner, state, etc., call the 'Admin/Get info Service' API (FETCH_PROJECT_INFO tool) and use the returned customListObjs IDs. 3. CRITICAL: For testsuiteOwner mapping - Call API 'Admin/Get info Service', from the response get value from customListObjs.owner[<index>].id. Match the user by customListObjs.owner[<index>].name. 4. If the user provides an owner name, fetch project info, find the matching user in customListObjs.owner[index].name, and use its ID in the payload as testsuiteOwner. If the name is not found, skip the testsuiteOwner field (it is not required) and show a user-friendly message: 'Test suite updated without owner, as given owner is not available in the current project.' 5. CRITICAL: For testSuiteState mapping - Call API 'Admin/Get info Service', from the response get value from customListObjs.testSuiteState[<index>].id. Match the state by customListObjs.testSuiteState[<index>].name. 6. If the user provides a test suite state name, fetch project info, find the matching state in customListObjs.testSuiteState[index].name, and use its ID in the payload as testSuiteState. If the name is not found, skip the testSuiteState field (it is not required) and show a user-friendly message: 'Test suite updated without test suite state, as given state is not available in the current project.' 7. If either owner or state is not found in project info, the update for that field will be skipped and a user-friendly message will be shown to the user. 8. UDF fields in steps must match your QMetry custom field configuration. 9. All IDs (testSuiteState from customListObjs.testSuiteState[index].id, testsuiteOwner from customListObjs.owner[index].id) must be valid for your QMetry instance. 10. If a custom field is mandatory, include it in the UDF object. 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_update_test_suite accept? +

qmetry_update_test_suite accepts 7 parameters: id, name, entityKey, TsFolderID, description, testSuiteState, testsuiteOwner. Required: id, entityKey, TsFolderID. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on qmetry_update_test_suite? +

Register the SmartBear MCP server in PolicyLayer and add a rule for qmetry_update_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_update_test_suite? +

qmetry_update_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_update_test_suite? +

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

Set action: deny in the PolicyLayer policy for qmetry_update_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_update_test_suite? +

qmetry_update_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

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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