AI agents call get_disk_usage to retrieve information from MCPHub without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves system information (disk usage metrics) with no apparent capability to modify, delete, or execute operations. It is a passive information retrieval function similar to other diagnostic tools in the server. Confidence is slightly reduced due to empty description, but the name strongly indicates a read operation. Severity is low as disk usage data is typically non-sensitive system metadata.
From the tool's definition Tool name 'get_disk_usage' indicates retrieval of disk usage statistics without modification. Naming convention and context (sibling tools include other information-gathering functions like 'get_env_vars', 'get_network_info', 'get_running_processes') suggest…
Attacks that exploit this kind of access
get_disk_usage. It is categorised as a Read tool in the MCPHub MCP Server, which means it retrieves data without modifying state.
Register the MCPHub MCP server in PolicyLayer and add a rule for get_disk_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 MCPHub. Nothing to install.
get_disk_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 get_disk_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 get_disk_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.
get_disk_usage is provided by the MCPHub MCP server (jayden-dong/mcphub). 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 →