get_managed_vps_details
A read tool on the 20i MCP server.
This record as markdown: /tools/cbrown35-20i-mcp/get-managed-vps-details.md
What get_managed_vps_details does on 20i MCP Server
AI agents call get_managed_vps_details to retrieve information from 20i MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_managed_vps_details is rated Low
This is a read operation that queries and retrieves VPS configuration or status data. However, the severity is medium rather than low because VPS details may include sensitive infrastructure information (IP addresses, resource allocations, configurations) that could be valuable for reconnaissance if an AI agent misuses it to map the hosting environment or identify attack surfaces.
From the tool's definition Tool name is 'get_managed_vps_details' and description states 'Get managed VPS details', indicating it retrieves information about virtual private servers without modifying state.
Attacks that exploit this kind of access
The rule that runs get_managed_vps_details safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 20i MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_managed_vps_details, this is the rule to start with:
get_managed_vps_details 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 20i MCP Server, apply this rule, and every get_managed_vps_details call is checked against it from then on.
Questions about get_managed_vps_details
get_managed_vps_details is a read tool on the 20i MCP Server MCP server. It is categorised as a Read tool in the 20i MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 20i MCP Server MCP server in PolicyLayer and add a rule for get_managed_vps_details: 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 20i MCP Server. Nothing to install.
get_managed_vps_details 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_managed_vps_details 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_managed_vps_details. 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_managed_vps_details is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 20i MCP Server, and thousands of servers like it.
This server
Across the catalogue