reflect_get_suite_execution_status
Get the status of a reflect suite execution Parameters: - suiteId (string) *required*: ID of the reflect suite to get execution status for - executionId (string) *required*: ID of the reflect suite execution to get status for
This record as markdown: /tools/smartbear-mcp/reflect-get-suite-execution-status.md
What reflect_get_suite_execution_status does on SmartBear MCP
AI agents call reflect_get_suite_execution_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 |
|---|---|---|---|
suiteId | string | Yes | ID of the reflect suite to get execution status for |
executionId | string | Yes | ID of the reflect suite execution to get status for |
Parameters from the server's own tool schema.
Why reflect_get_suite_execution_status is rated Low
This tool retrieves information about an existing test suite execution status. It takes two identifiers as input and returns status data with no side effects, state modifications, or external operations triggered. This is a straightforward read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name contains 'get' and description states 'Get the status of a reflect suite execution' — this is a query operation that retrieves execution status without modifying or triggering any state changes.
Attacks that exploit this kind of access
The rule that runs reflect_get_suite_execution_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 reflect_get_suite_execution_status, this is the rule to start with:
reflect_get_suite_execution_status 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 reflect_get_suite_execution_status call is checked against it from then on.
Questions about reflect_get_suite_execution_status
Get the status of a reflect suite execution Parameters: - suiteId (string) *required*: ID of the reflect suite to get execution status for - executionId (string) *required*: ID of the reflect suite execution to get status for. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
reflect_get_suite_execution_status accepts 2 parameters: suiteId, executionId. Required: suiteId, executionId. 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 reflect_get_suite_execution_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.
reflect_get_suite_execution_status 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 reflect_get_suite_execution_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.
Set action: deny in the PolicyLayer policy for reflect_get_suite_execution_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.
reflect_get_suite_execution_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.
More on SmartBear, and thousands of servers like it.
This server
Across the catalogue