reflect_cancel_suite_execution
Cancel a reflect suite execution Parameters: - suiteId (string) *required*: ID of the reflect suite to cancel execution for - executionId (string) *required*: ID of the reflect suite execution to cancel
This record as markdown: /tools/smartbear-mcp/reflect-cancel-suite-execution.md
What reflect_cancel_suite_execution does on SmartBear MCP
AI agents call reflect_cancel_suite_execution to permanently remove resources in SmartBear MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
suiteId | string | Yes | ID of the reflect suite to cancel execution for |
executionId | string | Yes | ID of the reflect suite execution to cancel |
Parameters from the server's own tool schema.
Why reflect_cancel_suite_execution is rated Critical
Cancelling a suite execution terminates an ongoing process permanently. Unlike a pause or stop that could be restarted from the same state, cancellation is irreversible — the execution is gone and would need to be re-triggered as a new run. This maps to Destructive rather than Write, as the action cannot be undone.
From the tool's definition 'Cancel a reflect suite execution' — cancelling an in-progress execution is irreversible; the cancelled run cannot be resumed or undone.
Attacks that exploit this kind of access
The rule that runs reflect_cancel_suite_execution 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_cancel_suite_execution, this is the rule to start with:
reflect_cancel_suite_execution is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every reflect_cancel_suite_execution call is checked against it from then on.
Questions about reflect_cancel_suite_execution
Cancel a reflect suite execution Parameters: - suiteId (string) *required*: ID of the reflect suite to cancel execution for - executionId (string) *required*: ID of the reflect suite execution to cancel. It is categorised as a Destructive tool in the SmartBear MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
reflect_cancel_suite_execution 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_cancel_suite_execution: 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_cancel_suite_execution is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the reflect_cancel_suite_execution 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_cancel_suite_execution. 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_cancel_suite_execution 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