检查存储桶是否存在
AI agents call bucket_exists to retrieve information from MinIO Storage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only checks whether a bucket exists, which is a read-only operation. It retrieves state information without modifying, creating, or deleting anything. Minimal blast radius if misused.
From the tool's definition 检查存储桶是否存在 (Check if bucket exists) — purely a existence check/query with no side effects
Attacks that exploit this kind of access
检查存储桶是否存在. It is categorised as a Read tool in the MinIO Storage MCP MCP Server, which means it retrieves data without modifying state.
Register the MinIO Storage MCP server in PolicyLayer and add a rule for bucket_exists: 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.
bucket_exists is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the bucket_exists 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 bucket_exists. 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.
bucket_exists 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 →