reflect_execute_suite
Execute a reflect suite Parameters: - suiteId (string) *required*: ID of the reflect suite to execute
This record as markdown: /tools/smartbear-mcp/reflect-execute-suite.md
What reflect_execute_suite does on SmartBear MCP
AI agents invoke reflect_execute_suite to trigger actions in SmartBear MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
suiteId | string | Yes | ID of the reflect suite to execute |
Parameters from the server's own tool schema.
Why reflect_execute_suite is rated High
This tool runs test suites, which is an external operation that performs actions whose effects depend on runtime behavior and suite configuration. While tests are typically read-only in terms of data retrieval, executing them can have side effects (API calls, database writes during test setup/teardown, external service interactions).
From the tool's definition Tool name 'reflect_execute_suite' with description 'Execute a reflect suite' — the verb 'Execute' directly indicates running/triggering an external operation.
Attacks that exploit this kind of access
The rule that runs reflect_execute_suite 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_execute_suite, this is the rule to start with:
reflect_execute_suite stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_execute_suite call is checked against it from then on.
Questions about reflect_execute_suite
Execute a reflect suite Parameters: - suiteId (string) *required*: ID of the reflect suite to execute. It is categorised as a Execute tool in the SmartBear MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
reflect_execute_suite accepts 1 parameter: suiteId. Required: suiteId. 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_execute_suite: 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_execute_suite is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the reflect_execute_suite 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_execute_suite. 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_execute_suite 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.
Across the catalogue