Get free disk space for a given path
AI agents call hydra_get_disk_free_space to retrieve information from Hydra Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns disk space information for a specified path. It performs no modifications to data or system state, no code execution, and no financial operations. It is a straightforward information retrieval (Read) operation with minimal risk even if misused, as the worst case would be repeatedly querying disk space.
From the tool's definition Tool name 'hydra_get_disk_free_space' and description 'Get free disk space for a given path' indicate a query operation that retrieves system information without modification or side effects.
Attacks that exploit this kind of access
Get free disk space for a given path. It is categorised as a Read tool in the Hydra Bridge MCP Server, which means it retrieves data without modifying state.
Register the Hydra Bridge MCP server in PolicyLayer and add a rule for hydra_get_disk_free_space: 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 Hydra Bridge. Nothing to install.
hydra_get_disk_free_space 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 hydra_get_disk_free_space 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 hydra_get_disk_free_space. 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.
hydra_get_disk_free_space is provided by the Hydra Bridge MCP server (kleirrampage45/hydra-bridge). 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 →