qmetry_set_qmetry_project_info

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 10 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/qmetry-set-qmetry-project-info.md

WHAT IT DOES

What qmetry_set_qmetry_project_info does on SmartBear MCP

AI agents use qmetry_set_qmetry_project_info 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
`projectKey`	string	—	Project key - unique identifier for the project

Parameters from the server's own tool schema.

RISK

Why qmetry_set_qmetry_project_info is rated Medium

This tool modifies the current project context for the user's session, which is a write operation (reversible configuration change). It does not delete data (not Destructive), does not execute arbitrary code (not Execute), does not move money (not Financial), and retrieves more than it modifies (not primarily Read).

From the tool's definition Tool name and description indicate it 'Set current QMetry project' and 'Switch to a specific project' — operations that modify session/account state.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

qmetry_set_qmetry_project_info Rate-limited

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

FAQ

Questions about qmetry_set_qmetry_project_info

What does the qmetry_set_qmetry_project_info tool do? +

Set current QMetry project for your account Parameters: - projectKey (string): Project key - unique identifier for the project (default: "default") Output Description: JSON object containing project configuration details, confirmation of project switch, and available project metadata Use Cases: 1. Switch to a specific project before performing test case operations 2. Set project context for batch operations on test cases 3. Configure the default project for the current session 4. Validate access to a specific project before proceeding with operations Examples: 1. Set default project as active json { "projectKey": "default" } Expected Output: Project context set to 'default' with confirmation of project details 2. Switch to UT project json { "projectKey": "UT" } Expected Output: Project context switched to 'UT' project with available configurations 3. Set MAC project as active for test case operations json { "projectKey": "MAC" } Expected Output: Project context set to 'MAC' with viewIds and folder structure Hints: 1. Always set the project context before performing test case operations in multi-project environments 2. Use the same project key that you'll use in subsequent test case operations 3. Common project keys include 'default', 'UT', 'MAC', 'VT' - check with your QMetry admin for available projects 4. This operation must be performed before fetching test cases if working with non-default projects 5. The project context persists for the current session until changed again. 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_set_qmetry_project_info accept? +

qmetry_set_qmetry_project_info accepts 1 parameter: projectKey. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on qmetry_set_qmetry_project_info? +

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

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

Can I rate-limit qmetry_set_qmetry_project_info? +

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

Set action: deny in the PolicyLayer policy for qmetry_set_qmetry_project_info. 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_set_qmetry_project_info? +

qmetry_set_qmetry_project_info 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

set-prioity on Kanban MCP Server →create_project on Stitch MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

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