qmetry_set_qmetry_project_info

// WHEN AI AGENTS USE THIS TOOL

AI agents use qmetry_set_qmetry_project_info to create or modify resources in SmartBear MCP. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON QMETRY_SET_QMETRY_PROJECT_INFO

Without a policy, an AI agent could call qmetry_set_qmetry_project_info repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach SmartBear MCP.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

smartbear-mcp.yaml

tools:
  qmetry_set_qmetry_project_info:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full SmartBear MCP policy for all 243 tools.

// DETAILS

Tool Name qmetry_set_qmetry_project_info

Category Write

MCP Server SmartBear MCP MCP Server

Risk Level Medium

// MORE SMARTBEAR MCP TOOLS

Destructive collaborator_delete_collaborator_remote_system_configuration Destructive contract-testing_admin_delete_role Destructive contract-testing_admin_delete_team Destructive contract-testing_admin_delete_user Destructive contract-testing_admin_remove_role_from_user Destructive contract-testing_admin_remove_user_from_team Destructive contract-testing_admin_reset_roles Destructive contract-testing_delete_all_integrations

View all 243 tools →

// WHAT CAN GO WRONG

Agents calling write-class tools like qmetry_set_qmetry_project_info have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Firecrawl Web Scraping Server firecrawl_generate_llmstxt AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update

// RELATED READING

// FAQ

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.

How do I enforce a policy on qmetry_set_qmetry_project_info? +

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

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

Let agents act without letting them run wild.