qmetry_fetch_qmetry_list_projects

// WHEN AI AGENTS USE THIS TOOL

AI agents call qmetry_fetch_qmetry_list_projects to retrieve information from SmartBear MCP without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON QMETRY_FETCH_QMETRY_LIST_PROJECTS

Even though qmetry_fetch_qmetry_list_projects only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

smartbear-mcp.yaml

tools:
  qmetry_fetch_qmetry_list_projects:
    rules:
      - action: allow

See the full SmartBear MCP policy for all 147 tools.

// DETAILS

Tool Name qmetry_fetch_qmetry_list_projects

Category Read

MCP Server SmartBear MCP MCP Server

Risk Level Low

// MORE SMARTBEAR MCP TOOLS

Destructive collaborator_delete_collaborator_remote_system_configuration Destructive reflect_cancel_suite_execution Destructive reflect_delete_previous_step Destructive swagger_delete_portal_product Destructive swagger_delete_table_of_contents Execute collaborator_reviewservice_action Execute contract-testing_can_i_deploy Execute qmetry_link_issues_to_testcase_run

View all 147 tools →

// RELATED READING

// FAQ

What does the qmetry_fetch_qmetry_list_projects tool do? +

Fetch QMetry projects list including projectID, name, projectKey, isArchived, viewIds and folderPath needed for other operations **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") - params (object) *required* - start (number): Start index for pagination - defaults to 0 (default: 0) - page (number): Page number to return (starts from 1) (default: 1) - limit (number): Number of records (default 10). (default: 10) - filter (string): Filter criteria as JSON string (default '[]') (default: "[]") **Output Description:** JSON object containing list of projects details **Use Cases:** 1. Get project list to check user how many project access to particular apikey 2. Retrieve available fields of each project list including projectID, name, projectKey, isArchived, viewIds and folderPath needed for other operations 3. Validate project access and permissions **Examples:** 1. Get list of project available to user ```json { "params": { "showArchive": false } } ``` Expected Output: Project active/non archived list including some important fields like projectID, name, projectKey, isArchived, viewIds and folderPath needed for other operations 2. Get projects with custom pagination ```json { "params": { "showArchive": false }, "page": 1, "limit": 10, "start": 0 } ``` Expected Output: List of projects with custom pagination settings 3. Get not active/archived projects ```json { "params": { "showArchive": true } } ``` Expected Output: List of all projects including archived ones (showArchive: true sent in payload) 4. Filter projects by name ```json { "filter": "[{\"value\":\"MAC\",\"type\":\"string\",\"field\":\"name\"}]" } ``` Expected Output: Filtered list of projects matching the name criteria 5. Filter projects by project key ```json { "filter": "[{\"value\":\"MAC\",\"type\":\"string\",\"field\":\"projectKey\"}]" } ``` Expected Output: List of projects filtered by project key (e.g. 'MAC', 'UT', etc.) **Hints:** 1. Fetch list of projects available to user 2. Use 'default' project key when user doesn't specify one 3. Use params.showArchive: true/false to get archived/non-archived projects, default is false when not provided 4. Pagination supported for large result sets (start, page, limit parameters) 5. Filter parameter should be a JSON string with filter criteria 6. Common filter fields: 'name' (string), 'projectKey' (string). It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on qmetry_fetch_qmetry_list_projects? +

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

qmetry_fetch_qmetry_list_projects is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit qmetry_fetch_qmetry_list_projects? +

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

Set action: deny in the Intercept policy for qmetry_fetch_qmetry_list_projects. 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_fetch_qmetry_list_projects? +

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

qmetry_fetch_qmetry_list_projects

Enforce policies on SmartBear MCP