qmetry_fetch_qmetry_list_projects

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.

qmetry_fetch_qmetry_list_projects accepts 7 parameters: page, limit, start, filter, params, baseUrl, projectKey. Required: params. The full parameter table on this page comes from the server's own tool schema.

Register the SmartBear MCP server in PolicyLayer and add a rule for qmetry_fetch_qmetry_list_projects: 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.

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

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

Set action: deny in the PolicyLayer 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.

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