AI agents call qnap_storage_usage to retrieve information from Homelab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays storage usage information—a passive data query with no side effects. It does not create, modify, delete, or execute any operations. The severity is low because the blast radius of misuse is limited to information disclosure, which in a homelab context poses minimal risk.
From the tool's definition The tool name 'qnap_storage_usage' and description 'Show detailed storage usage for all QNAP shares and LVM volume group' indicate a read-only operation that queries and retrieves storage metrics without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
Show detailed storage usage for all QNAP shares and LVM volume group. It is categorised as a Read tool in the Homelab MCP Server, which means it retrieves data without modifying state.
Register the Homelab MCP server in PolicyLayer and add a rule for qnap_storage_usage: 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 Homelab. Nothing to install.
qnap_storage_usage 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 qnap_storage_usage 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 qnap_storage_usage. 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.
qnap_storage_usage is provided by the Homelab MCP server (nainounen/homelab-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 →