Delete a saved scenario. Permanent, cannot be undone.
AI agents call delete_scenario to permanently remove resources in Sablier MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes stored scenario data with no recovery mechanism. While the financial impact depends on the scenario's importance, the permanent loss of analysis work, modeling assumptions, or historical scenario comparisons could be material to investment decision-making.
From the tool's definition Tool description explicitly states: 'Delete a saved scenario. Permanent, cannot be undone.' The words 'Permanent' and 'cannot be undone' are definitive indicators of irreversible data deletion.
Attacks that exploit this kind of access
Delete a saved scenario. Permanent, cannot be undone. It is categorised as a Destructive tool in the Sablier MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sablier MCP Server MCP server in PolicyLayer and add a rule for delete_scenario: 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 Sablier MCP Server. Nothing to install.
delete_scenario 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 delete_scenario 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 delete_scenario. 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.
delete_scenario is provided by the Sablier MCP Server MCP server (sablier-ai/sablier-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →