reflect_delete_previous_step
Delete the last step added to an active Reflect recording session Parameters: - sessionId (string) *required*: The ID of the Reflect recording session
This record as markdown: /tools/smartbear-mcp/reflect-delete-previous-step.md
What reflect_delete_previous_step does on SmartBear MCP
AI agents call reflect_delete_previous_step 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 |
|---|---|---|---|
sessionId | string | Yes | The ID of the Reflect recording session |
Parameters from the server's own tool schema.
Why reflect_delete_previous_step is rated Critical
The tool performs a deletion action ('delete_previous_step') that cannot be undone. Once a step is deleted from a Reflect recording session, it is removed permanently. While the blast radius is somewhat limited (only affects the current recording session), the destructive nature of permanent data removal classifies it as Destructive rather than Write. This is more severe than a reversible modification.
From the tool's definition Tool name contains 'delete' and description states 'Delete the last step added to an active Reflect recording session' — this is an irreversible deletion operation that removes data from a recording.
Attacks that exploit this kind of access
The rule that runs reflect_delete_previous_step 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_delete_previous_step, this is the rule to start with:
reflect_delete_previous_step 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_delete_previous_step call is checked against it from then on.
Questions about reflect_delete_previous_step
Delete the last step added to an active Reflect recording session Parameters: - sessionId (string) *required*: The ID of the Reflect recording session. 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_delete_previous_step accepts 1 parameter: sessionId. Required: sessionId. 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_delete_previous_step: 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_delete_previous_step 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_delete_previous_step 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_delete_previous_step. 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_delete_previous_step 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