qmetry_fetch_automation_status

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Low RISK CLASS

Category Read

Parameters 31 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/qmetry-fetch-automation-status.md

WHAT IT DOES

What qmetry_fetch_automation_status does on SmartBear MCP

AI agents call qmetry_fetch_automation_status 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
`baseUrl`	string	—	The base URL for the QMetry instance (must be a valid URL)
`requestID`	number	Yes	Numeric request ID from import automation response
`projectKey`	string	—	Project key - unique identifier for the project

Parameters from the server's own tool schema.

RISK

Why qmetry_fetch_automation_status is rated Low

This tool retrieves status information about an existing automation import job. It performs a read-only query operation to check progress and details. No data is created, modified, deleted, or executed; the tool only queries and returns status information. This is a low-severity read operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool description states it 'Fetches the status' and 'Retrieve status, progress, and details' — purely query/retrieval operations with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

qmetry_fetch_automation_status Allowed

qmetry_fetch_automation_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "qmetry_fetch_automation_status": {}
  }
}

ALLOW ONLY 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_fetch_automation_status call is checked against it from then on.

FAQ

Questions about qmetry_fetch_automation_status

What does the qmetry_fetch_automation_status tool do? +

Fetches the status of an automation import job by request ID. 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") - requestID (number) *required*: Numeric request ID from import automation response Use Cases: 1. 1. Check if an automation import job is completed or still in progress. 2. 2. Retrieve status, progress, and details for a specific automation import request. 3. 3. Monitor automation result processing for CI/CD integrations. Examples: 1. Fetch status for request ID 12345 json { "requestID": 12345 } Expected Output: Status, progress, and details of the automation import job for request ID 12345. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.

What parameters does qmetry_fetch_automation_status accept? +

qmetry_fetch_automation_status accepts 3 parameters: baseUrl, requestID, projectKey. Required: requestID. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on qmetry_fetch_automation_status? +

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

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

Can I rate-limit qmetry_fetch_automation_status? +

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

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

qmetry_fetch_automation_status 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

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →