删除存储桶策略
AI agents call delete_bucket_policy to permanently remove resources in MinIO Storage MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a bucket policy is a destructive action that cannot be easily undone. It removes security configurations that control who can access the bucket and what operations they can perform. An AI agent misusing this tool could inadvertently strip permissions from a bucket, preventing legitimate users from accessing critical data or enabling unauthorized access.
From the tool's definition Tool name is 'delete_bucket_policy' and description translates to 'delete bucket policy'. This irreversibly removes access control policies from a MinIO bucket.
Attacks that exploit this kind of access
删除存储桶策略. It is categorised as a Destructive tool in the MinIO Storage MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MinIO Storage MCP server in PolicyLayer and add a rule for delete_bucket_policy: 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 MinIO Storage MCP. Nothing to install.
delete_bucket_policy 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_bucket_policy 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_bucket_policy. 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_bucket_policy is provided by the MinIO Storage MCP server (pickstar-2002/minio-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 →