qmetry_fetch_qmetry_project_info
Fetch QMetry project information including viewId and folderPath needed for other operations Parameters: - projectKey (string): Project key - unique identifier for the project (default: "default") Output Description: JSON object containing project details, viewIds, folderPaths, and project config...
This record as markdown: /tools/smartbear-mcp/qmetry-fetch-qmetry-project-info.md
What qmetry_fetch_qmetry_project_info does on SmartBear MCP
AI agents call qmetry_fetch_qmetry_project_info to retrieve information from SmartBear MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
projectKey | string | — | Project key - unique identifier for the project |
Parameters from the server's own tool schema.
Why qmetry_fetch_qmetry_project_info is rated Low
This is a read-only query operation that retrieves metadata about QMetry projects. It has no side effects, cannot modify or delete data, and does not execute arbitrary code. The blast radius of misuse is minimal—an attacker would only gain visibility into project structure and configuration already accessible to the authenticated user. Classified as Read with low severity.
From the tool's definition Tool fetches and retrieves project information including viewId, folderPath, and project configuration. Described as 'Fetch QMetry project information' with use cases focused on retrieval: 'Get project configuration', 'Retrieve available viewIds', 'Get…
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs qmetry_fetch_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_fetch_qmetry_project_info, this is the rule to start with:
qmetry_fetch_qmetry_project_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every qmetry_fetch_qmetry_project_info call is checked against it from then on.
Questions about qmetry_fetch_qmetry_project_info
Fetch QMetry project information including viewId and folderPath needed for other operations Parameters: - projectKey (string): Project key - unique identifier for the project (default: "default") Output Description: JSON object containing project details, viewIds, folderPaths, and project configuration Use Cases: 1. Get project configuration before fetching test cases 2. Retrieve available viewIds for test case listing 3. Get folderPath information for project navigation 4. Validate project access and permissions Examples: 1. Get default project info json {} Expected Output: Project configuration with viewIds, folderPaths, and project details 2. Get specific project info json { "projectKey": "MAC" } Expected Output: MAC project configuration with available views and folders Hints: 1. Always call this first when user doesn't provide viewId or folderPath 2. Use 'default' project key when user doesn't specify one 3. Extract viewId from latestViews.TC.viewId for test case operations 4. Use empty string '' as folderPath for root directory. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
qmetry_fetch_qmetry_project_info accepts 1 parameter: projectKey. 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_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.
qmetry_fetch_qmetry_project_info 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_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.
Set action: deny in the PolicyLayer policy for qmetry_fetch_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.
qmetry_fetch_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.
More on SmartBear, and thousands of servers like it.
This server
Across the catalogue