This record as markdown: /tools/cbrown35-20i-mcp/deactivate-vps.md
What deactivate_vps does on 20i MCP Server
AI agents call deactivate_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 deactivate_vps is rated Critical
Deactivating a VPS terminates the running virtual server environment, taking down all hosted services, websites, databases, and applications on it. This is a highly destructive action with critical blast radius — it cannot be easily undone without re-provisioning, and paired with the sibling tool 'activate_vps', deactivation implies a full shutdown of the VPS.
From the tool's definition 'Deactivate VPS service' - deactivating a VPS is an irreversible or highly disruptive action that brings down the virtual private server and all services running on it
Attacks that exploit this kind of access
The rule that runs deactivate_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 deactivate_vps, this is the rule to start with:
deactivate_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 deactivate_vps call is checked against it from then on.
Questions about deactivate_vps
Deactivate VPS service. 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 deactivate_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.
deactivate_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 deactivate_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 deactivate_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.
deactivate_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