Legacy compatibility - Get disk usage information from Linux host
AI agents call get_disk_usage to retrieve information from SSH MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves disk usage data from a remote system, which is a read-only operation with no side effects. The description explicitly states it gets information (retrieves data) rather than executes commands or modifies system state. Despite being on an SSH MCP server with dangerous sibling tools (execute_ssh, execute_sudo), this specific tool is limited to information retrieval.
From the tool's definition Tool name 'get_disk_usage' and description 'Get disk usage information from Linux host' indicate a read-only query operation that retrieves system metrics without modification or command execution.
Attacks that exploit this kind of access
Legacy compatibility - Get disk usage information from Linux host. It is categorised as a Read tool in the SSH MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SSH MCP Server 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 SSH MCP Server. 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 SSH MCP Server MCP server (inframcp/ssh-mcp-server). 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 →