# enable_vpn_gateway

A write tool on the CloudStack MCP Server MCP server.

Agent View of the PolicyLayer registry record for `enable_vpn_gateway`. HTML page: https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/enable-vpn-gateway

## Facts

- Tool: `enable_vpn_gateway`
- Server: CloudStack MCP Server (`mozg31337/cloudstack-mcp-server`) — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server.md
- Homepage: https://github.com/mozg31337/cloudstack-mcp-server
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "enable_vpn_gateway",
    "arguments": {}
  }
}
```

## Why enable_vpn_gateway is rated Medium

Enabling a VPN gateway modifies the state of a network component by activating it, which is a reversible write operation. It does not delete data, execute arbitrary code, or involve financial transactions. Misuse could expose network segments but the action itself is reversible.

From the tool's own definition: "'Enable VPN gateway' - enabling a service is a reversible configuration change (it can be disabled again)"

## Use case

AI agents use enable_vpn_gateway to create or update resources in CloudStack MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CloudStack MCP Server environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches CloudStack MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "enable_vpn_gateway": {
      "limits": [
        {
          "counter": "enable_vpn_gateway_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on CloudStack MCP Server (441)

- `cancel_host_maintenance` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/cancel-host-maintenance.md
- `delete_account` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-account.md
- `delete_account_from_project` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-account-from-project.md
- `delete_alerts` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-alerts.md
- `delete_application_load_balancer` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-application-load-balancer.md
- `delete_bgp_peer` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-bgp-peer.md
- `delete_customer_gateway` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-customer-gateway.md
- `delete_dhcp_option` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-dhcp-option.md
- `delete_disk_offering` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-disk-offering.md
- `delete_domain` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-domain.md
- `delete_egress_firewall_rule` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-egress-firewall-rule.md
- `delete_firewall_rule` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-firewall-rule.md
- `delete_global_load_balancer` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-global-load-balancer.md
- `delete_host` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-host.md
- `delete_image_store` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-image-store.md
- `delete_ip_forwarding_rule` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-ip-forwarding-rule.md
- `delete_ipv4_subnet_for_guest_network` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-ipv4-subnet-for-guest-network.md
- `delete_ipv4_subnet_for_zone` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-ipv4-subnet-for-zone.md
- `delete_ipv6_firewall_rule` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-ipv6-firewall-rule.md
- `delete_iso` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-iso.md
- `delete_kubernetes_cluster` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-kubernetes-cluster.md
- `delete_kubernetes_supported_version` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-kubernetes-supported-version.md
- `delete_lb_health_check_policy` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-lb-health-check-policy.md
- `delete_lb_stickiness_policy` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-lb-stickiness-policy.md
- `delete_load_balancer_rule` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-load-balancer-rule.md
- `delete_network` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-network.md
- `delete_network_acl` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-network-acl.md
- `delete_network_acl_list` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-network-acl-list.md
- `delete_network_device` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-network-device.md
- `delete_network_offering` — Destructive — https://policylayer.com/tools/mozg31337-cloudstack-mcp-server/delete-network-offering.md
- …and 411 more: https://policylayer.com/tools/mozg31337-cloudstack-mcp-server.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=mozg31337-cloudstack-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/mozg31337-cloudstack-mcp-server
