# proxmox_terraform_plan

Execute Terraform plans for infrastructure as code

Agent View of the PolicyLayer registry record for `proxmox_terraform_plan`. HTML page: https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-terraform-plan

## Facts

- Tool: `proxmox_terraform_plan`
- Server: MCP Proxmox Server (`bsahane/mcp-proxmox`) — https://policylayer.com/tools/bsahane-mcp-proxmox.md
- Homepage: https://github.com/bsahane/mcp-proxmox
- Risk category: Execute (High 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": "proxmox_terraform_plan",
    "arguments": {}
  }
}
```

## Why proxmox_terraform_plan is rated High

Terraform plan execution runs infrastructure-as-code operations that can provision, modify, or destroy virtualization resources. While 'plan' in Terraform typically previews changes without applying them, this tool description says 'execute' Terraform plans which implies actually running/applying infrastructure changes.

From the tool's own definition: "'Execute Terraform plans for infrastructure as code'"

## Use case

AI agents invoke proxmox_terraform_plan to trigger actions in MCP Proxmox Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "proxmox_terraform_plan": {
      "limits": [
        {
          "counter": "proxmox_terraform_plan_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on MCP Proxmox Server (123)

- `proxmox_delete_lxc` — Destructive — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-delete-lxc.md
- `proxmox_delete_pool` — Destructive — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-delete-pool.md
- `proxmox_delete_snapshot` — Destructive — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-delete-snapshot.md
- `proxmox_delete_vm` — Destructive — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-delete-vm.md
- `proxmox_docker_service_remove` — Destructive — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-docker-service-remove.md
- `proxmox_lxc_notes_remove` — Destructive — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-lxc-notes-remove.md
- `proxmox_pool_remove` — Destructive — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-pool-remove.md
- `proxmox_rollback_snapshot` — Destructive — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-rollback-snapshot.md
- `proxmox_shutdown_vm` — Destructive — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-shutdown-vm.md
- `proxmox_vm_nic_remove` — Destructive — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-vm-nic-remove.md
- `proxmox_vm_notes_remove` — Destructive — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-vm-notes-remove.md
- `proxmox_ai_scaling` — Execute — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-ai-scaling.md
- `proxmox_ansible_playbook` — Execute — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-ansible-playbook.md
- `proxmox_api_gateway` — Execute — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-api-gateway.md
- `proxmox_auto_optimize` — Execute — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-auto-optimize.md
- `proxmox_create_docker_swarm` — Execute — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-create-docker-swarm.md
- `proxmox_create_docker_swarm_preset` — Execute — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-create-docker-swarm-preset.md
- `proxmox_deploy_openshift_cluster` — Execute — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-deploy-openshift-cluster.md
- `proxmox_deploy_openshift_sno` — Execute — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-deploy-openshift-sno.md
- `proxmox_deploy_vpn_server` — Execute — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-deploy-vpn-server.md
- `proxmox_docker_execute_command` — Execute — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-docker-execute-command.md
- `proxmox_docker_service_create` — Execute — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-docker-service-create.md
- `proxmox_docker_service_scale` — Execute — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-docker-service-scale.md
- `proxmox_docker_swarm_init` — Execute — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-docker-swarm-init.md
- `proxmox_docker_swarm_join` — Execute — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-docker-swarm-join.md
- `proxmox_gitops_sync` — Execute — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-gitops-sync.md
- `proxmox_guest_exec` — Execute — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-guest-exec.md
- `proxmox_integrate_service` — Execute — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-integrate-service.md
- `proxmox_migrate_storage` — Execute — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-migrate-storage.md
- `proxmox_migrate_vm` — Execute — https://policylayer.com/tools/bsahane-mcp-proxmox/proxmox-migrate-vm.md
- …and 93 more: https://policylayer.com/tools/bsahane-mcp-proxmox.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=bsahane-mcp-proxmox · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/bsahane-mcp-proxmox
