Delete a portfolio by ID. Permanent, cannot be undone.
AI agents call delete_portfolio 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 permanently removes user data (a portfolio) and explicitly cannot be reversed. This fits the Destructive category definition: irreversibly deletes data and actions that cannot be undone. High severity due to potential data loss, though confined to a single portfolio rather than system-wide impact. High confidence based on explicit description of permanent deletion.
From the tool's definition Tool description explicitly states: "Delete a portfolio by ID. Permanent, cannot be undone." The name "delete_portfolio" and the irreversible nature of the operation directly indicate destructive action.
Attacks that exploit this kind of access
Delete a portfolio by ID. 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_portfolio: 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_portfolio 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_portfolio 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_portfolio. 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_portfolio 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 →