check_minio
Check MinIO object storage availability via GET /minio/health/live (liveness) and /minio/health/ready (readiness). Port 9000 = default, 9001 = console. Returns liveness and readiness status separately.
This record as markdown: /tools/aaronckj-mcp-nettools/check-minio.md
What check_minio does on Mcp Nettools
AI agents call check_minio to retrieve information from Mcp Nettools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_minio is rated Low
This tool only retrieves health and status information from a MinIO instance using standard HTTP GET requests to health check endpoints. It has no side effects, does not create, modify, or delete data, and does not execute commands or trigger external operations. It is purely a diagnostic read operation, similar to other network diagnostic tools on this server like ping or cert_check.
From the tool's definition Tool performs health checks via GET requests to /minio/health/live and /minio/health/ready endpoints, returning status information without modifying data.
Attacks that exploit this kind of access
The rule that runs check_minio safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_minio, this is the rule to start with:
check_minio 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 Mcp Nettools, apply this rule, and every check_minio call is checked against it from then on.
Questions about check_minio
Check MinIO object storage availability via GET /minio/health/live (liveness) and /minio/health/ready (readiness). Port 9000 = default, 9001 = console. Returns liveness and readiness status separately. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.
Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_minio: 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 Mcp Nettools. Nothing to install.
check_minio 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 check_minio 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 check_minio. 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.
check_minio is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Nettools, and thousands of servers like it.
This server
Across the catalogue