storage_status
Show MinIO status (running, endpoint, buckets, total size).
This record as markdown: /tools/io-github-kivanccakmak-yaver/storage-status.md
What storage_status does on Yaver
AI agents call storage_status to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why storage_status is rated Low
This is a purely informational query operation that retrieves and displays the current state of a MinIO storage service. It does not create, modify, delete, or execute any operations — it only reads and reports status metrics. The blast radius of misuse is minimal; an agent learning bucket names or storage capacity poses no immediate harm.
From the tool's definition Tool name is 'storage_status' and description states 'Show MinIO status' — retrieves information about storage system state (running status, endpoint, buckets, total size) with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs storage_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For storage_status, this is the rule to start with:
storage_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every storage_status call is checked against it from then on.
Questions about storage_status
Show MinIO status (running, endpoint, buckets, total size). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
Register the Yaver MCP server in PolicyLayer and add a rule for storage_status: 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 Yaver. Nothing to install.
storage_status 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 storage_status 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 storage_status. 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.
storage_status is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue