Delete a Tigris bucket in your account
AI agents call tigris_delete_bucket to permanently remove resources in Tigris — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Bucket deletion is a destructive operation that cannot be undone and permanently removes data storage infrastructure and associated objects. This ranks above Execute because the action is inherently irreversible, and above Write because it destroys rather than modifies. High severity reflects the potential loss of substantial amounts of user data and service disruption if misused by an agent.
From the tool's definition Tool name 'tigris_delete_bucket' combined with description 'Delete a Tigris bucket in your account' explicitly indicates irreversible deletion of entire bucket storage containers and all their contents.
Attacks that exploit this kind of access
Delete a Tigris bucket in your account. It is categorised as a Destructive tool in the Tigris MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tigris MCP server in PolicyLayer and add a rule for tigris_delete_bucket: 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 Tigris. Nothing to install.
tigris_delete_bucket 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 tigris_delete_bucket 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 tigris_delete_bucket. 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.
tigris_delete_bucket is provided by the Tigris MCP server (@tigrisdata/tigris-mcp-server). 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 →