qmetry_create_test_suite

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 82 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What qmetry_create_test_suite does on SmartBear MCP

AI agents use qmetry_create_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
`name`	string	Yes
`description`	string	—
`parentFolderId`	string	Yes
`testSuiteState`	number	—
`testsuiteOwner`	number	—
`associateRelCyc`	boolean	—
`isAutomatedFlag`	boolean	—
`releaseCycleMapping`	array	—

Parameters from the server's own tool schema.

RISK

Why qmetry_create_test_suite is rated Medium

This tool creates and persists a new test suite entity with metadata and associations. It is a reversible write operation (the test suite can be deleted or modified later). It does not execute arbitrary code, delete data irreversibly, or move funds.

From the tool's definition Tool name includes 'create', description states 'Create a new test suite in QMetry' and returns 'new test suite ID, summary, and creation metadata'. Parameters include parentFolderId, name, description, owner, and state settings.

Risk signalsHigh parameter count (10 properties) · Admin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

qmetry_create_test_suite Rate-limited

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

FAQ

Questions about qmetry_create_test_suite

What does the qmetry_create_test_suite tool do? +

Create a new test suite in QMetry with metadata and release/cycle mapping. Parameters: - parentFolderId (string) *required* - name (string) *required* - isAutomatedFlag (boolean) - description (string) - testsuiteOwner (number) - testSuiteState (number) - associateRelCyc (boolean) - releaseCycleMapping (array) Output Description: JSON object containing the new test suite ID, summary, and creation metadata. Use Cases: 1. Create a basic test suite with just a name and folder 2. Add detailed metadata like description to a test suite 3. Associate test suite with specific release/cycle for planning 4. Set testsuiteOwner, testSuiteState, and other metadata using valid IDs from project info 5. Create test suites for isAutomatedFlag true or false for automated or manual types, default is false 6. Add test suite to a specific folder using parentFolderId 7. Map test suite to multiple cycles/releases and build ID Examples: 1. Create a test suite in the root folder (auto-resolved) json { "name": "Demo Test Suite" } Expected Output: Test suite created in the root test suite folder with ID and summary details 2. Create a simple test suite in folder 102653 json { "parentFolderId": "102653", "name": "Login Test Suite" } Expected Output: Test suite created with ID and summary details 3. Create a test suite with some details and metadata json { "parentFolderId": "113557", "isAutomatedFlag": false, "name": "Testsuite Summary", "description": "desc", "testsuiteOwner": 6963, "testSuiteState": 505035, "associateRelCyc": true, "releaseCycleMapping": [ { "buildID": 18411, "releaseId": 10286 } ] } Expected Output: Test suite created with details and metadata. Example uses: parentFolderId=113557 (MAC root TS folder from rootFolders.TS.id), testsuiteOwner=6963 (umang.savaliya from customListObjs.owner[index].id), testSuiteState=505035 (New from customListObjs.testSuiteState[index].id), releaseId=10286 (Air release from projects[index].releases[index].releaseID), buildID=18411 (Air Q1-19 cycle from projects[index].releases[index].builds[index].buildID) Hints: 1. If parentFolderId is not provided, it will be auto-resolved to the root test suite folder using project info (rootFolders.TS.id). 2. To get valid values for testsuiteOwner, testSuiteState, 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 (testsuiteOwner), fetch project info, find the matching owner in customListObjs.owner[index].name or customListObjs.owner[index].uniqueLabel, 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 created 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(testSuiteState), 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 created without test suite state, as given state is not available in the current project.' 7. parentFolderId is required; use the root folder ID from project info (rootFolders.TS.id) or a specific folder. 8. Release/cycle mapping is optional but useful for planning. 9. If the user wants to link or associate a release and cycle to the test suite, set associateRelCyc: true in the payload. 10. CRITICAL: For releaseCycleMapping.releaseId - Call API 'Release/List' (or use project info projects[<index>].releases[<index>].releaseID), from the response get value from data[<index>].releaseID or projects[<index>].releases[<index>].releaseID. Match the release by name. 11. CRITICAL: For releaseCycleMapping.buildID - Call API 'Cycle/List' (or use project info projects[<index>].releases[<index>].builds[<index>].buildID), from the response get value from data[<index>].buildID or projects[<index>].releases[<index>].builds[<index>].buildID. Match the build/cycle by name. 12. If the user provides a release name, map it to its ID from projects[<index>].releases[<index>].releaseID in the project info response, and use that ID as releaseId in releaseCycleMapping. 13. If the user provides a build/cycle name, map it to its ID from projects[<index>].releases[<index>].builds[<index>].buildID in the project info response, and use that ID as buildID in releaseCycleMapping. 14. Example payload: releaseCycleMapping: [ { releaseId: <releaseID>, buildID: <buildID> } ] 15. Example: For 'Air' release and 'Air Q1-19' cycle in MAC project, use releaseId: 10286 and buildID: 18411 16. LLM should ensure that provided release/cycle names or IDs exist in the current project before using them in the payload. If not found, skip and show a user-friendly message: 'Test suite created without release/cycle association, as given release/cycle is not available in the current project.' 17. All IDs (testSuiteState from customListObjs.testSuiteState[index].id, testsuiteOwner from customListObjs.owner[index].id, releaseId from projects.releases[index].releaseID, buildID from projects.releases.builds[index].buildID) must be valid for your QMetry instance. 18. 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_create_test_suite accept? +

qmetry_create_test_suite accepts 8 parameters: name, description, parentFolderId, testSuiteState, testsuiteOwner, associateRelCyc, isAutomatedFlag, releaseCycleMapping. Required: name, parentFolderId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on qmetry_create_test_suite? +

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

qmetry_create_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_create_test_suite? +

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

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

qmetry_create_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

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

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