rebuild_vps
Rebuild VPS with new configuration (DESTRUCTIVE)
This record as markdown: /tools/cbrown35-20i-mcp/rebuild-vps.md
What rebuild_vps does on 20i MCP Server
AI agents call rebuild_vps to permanently remove resources in 20i MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why rebuild_vps is rated Critical
Rebuilding a VPS destroys all existing data, configurations, and installed software on the virtual private server, replacing it with a fresh image. This is an irreversible operation with maximum blast radius — loss of all hosted websites, databases, emails, and configurations on that VPS.
From the tool's definition 'Rebuild VPS with new configuration (DESTRUCTIVE)' — the word DESTRUCTIVE is explicitly stated, and rebuilding a VPS overwrites the entire server environment irreversibly.
Attacks that exploit this kind of access
The rule that runs rebuild_vps 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 rebuild_vps, this is the rule to start with:
rebuild_vps is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect 20i MCP Server, apply this rule, and every rebuild_vps call is checked against it from then on.
Questions about rebuild_vps
Rebuild VPS with new configuration (DESTRUCTIVE). It is categorised as a Destructive tool in the 20i MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the 20i MCP Server MCP server in PolicyLayer and add a rule for rebuild_vps: 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.
rebuild_vps is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the rebuild_vps 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 rebuild_vps. 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.
rebuild_vps 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.
Across the catalogue