Remove VPN user
AI agents call remove_vpn_user to permanently remove resources in CloudStack MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a VPN user deletes credentials and access rights that cannot be automatically restored without administrative re-provisioning. This is a destructive operation with blast radius affecting authentication and access control. While the server mentions a safety confirmation system for destructive operations, the tool itself performs an irreversible deletion.
From the tool's definition Tool name is 'remove_vpn_user' and description states 'Remove VPN user' — the verb 'remove' indicates deletion of a user account or VPN access credential, which is irreversible.
Attacks that exploit this kind of access
Remove VPN user. It is categorised as a Destructive tool in the CloudStack MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for remove_vpn_user: 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 CloudStack MCP Server. Nothing to install.
remove_vpn_user 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 remove_vpn_user 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 remove_vpn_user. 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.
remove_vpn_user is provided by the CloudStack MCP Server MCP server (mozg31337/cloudstack-mcp-server). 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 →