infomaniak_get_vps_full
Full VPS / Cloud Server detail: location (datacenter), managed/lite flags, IPv4 + IPv6, CPU/RAM/perf, bandwidth + traffic, disk usage (total/assigned/used/database), website/hosting counts, MySQL version + database type, PHP versions, firewall config, premium support contacts (email/url/emergency...
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-get-vps-full.md
What infomaniak_get_vps_full does on Infomaniak Admin
AI agents call infomaniak_get_vps_full to retrieve information from Infomaniak Admin without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why infomaniak_get_vps_full is rated Low
The tool performs read-only operations to fetch comprehensive VPS metadata and configuration information. While the data returned is detailed and sensitive (support contacts, infrastructure details), the tool itself cannot modify, delete, or execute actions. The severity is low because information disclosure alone, without write/execute capabilities, presents limited immediate risk.
From the tool's definition Tool retrieves VPS/Cloud Server details including location, CPU/RAM, disk usage, configurations, and support contacts. No modifications, deletions, or code execution—purely informational queries of existing system state.
Attacks that exploit this kind of access
The rule that runs infomaniak_get_vps_full safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Infomaniak Admin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For infomaniak_get_vps_full, this is the rule to start with:
infomaniak_get_vps_full is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Infomaniak Admin, apply this rule, and every infomaniak_get_vps_full call is checked against it from then on.
Questions about infomaniak_get_vps_full
Full VPS / Cloud Server detail: location (datacenter), managed/lite flags, IPv4 + IPv6, CPU/RAM/perf, bandwidth + traffic, disk usage (total/assigned/used/database), website/hosting counts, MySQL version + database type, PHP versions, firewall config, premium support contacts (email/url/emergency), migration history. Use after. It is categorised as a Read tool in the Infomaniak Admin MCP Server, which means it retrieves data without modifying state.
Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_get_vps_full: 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 Infomaniak Admin. Nothing to install.
infomaniak_get_vps_full 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 infomaniak_get_vps_full 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 infomaniak_get_vps_full. 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.
infomaniak_get_vps_full is provided by the Infomaniak Admin MCP server (henrikogaard/infomaniak-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Infomaniak Admin, and thousands of servers like it.
This server
Across the catalogue