批量删除存储桶中的对象
AI agents call delete_objects 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.
This tool permanently and irreversibly removes multiple objects from cloud storage. Batch deletion amplifies the blast radius compared to single deletions—an AI agent could unintentionally destroy large volumes of data in a single call if provided incorrect parameters. This cannot be undone, making it Destructive rather than Write or Execute.
From the tool's definition Tool name 'delete_objects' combined with description '批量删除存储桶中的对象' (batch delete objects in storage bucket). The term 'delete' in the name and '删除' (delete) in the description explicitly indicate irreversible removal of data.
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_objects: 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_objects 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_objects 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_objects. 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_objects 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 →