AI agents call get_network to retrieve information from Hcloud without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves network configuration data by ID without modifying, creating, or deleting resources. It is a straightforward read operation with minimal blast radius if misused by an AI agent, as it only exposes existing network information.
From the tool's definition Tool name 'get_network' and description 'Get a single network by ID' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get a single network by ID. It is categorised as a Read tool in the Hcloud MCP Server, which means it retrieves data without modifying state.
Register the Hcloud MCP server in PolicyLayer and add a rule for get_network: 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 Hcloud. Nothing to install.
get_network 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_network 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_network. 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_network is provided by the Hcloud MCP server (xodus-co/hcloud-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 →