proxmox_docker_network_create
Create Docker network in Swarm cluster.
This record as markdown: /tools/bsahane-mcp-proxmox/proxmox-docker-network-create.md
What proxmox_docker_network_create does on MCP Proxmox Server
AI agents use proxmox_docker_network_create to create or update resources in MCP Proxmox Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Proxmox Server environment.
Why proxmox_docker_network_create is rated Medium
This tool creates a new Docker network resource in a Swarm cluster, which is a reversible write operation. While it modifies infrastructure state and could have wide blast radius if misconfigured (affecting all services using that network), it does not execute arbitrary code, delete resources permanently, or move financial assets.
From the tool's definition Tool name indicates 'create' operation: 'proxmox_docker_network_create'. Description states: 'Create Docker network in Swarm cluster.' The verb 'Create' denotes a write operation that modifies cluster state by adding a new network resource.
Attacks that exploit this kind of access
The rule that runs proxmox_docker_network_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Proxmox Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For proxmox_docker_network_create, this is the rule to start with:
proxmox_docker_network_create stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Proxmox Server, apply this rule, and every proxmox_docker_network_create call is checked against it from then on.
Questions about proxmox_docker_network_create
Create Docker network in Swarm cluster. It is categorised as a Write tool in the MCP Proxmox Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Proxmox Server MCP server in PolicyLayer and add a rule for proxmox_docker_network_create: 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 MCP Proxmox Server. Nothing to install.
proxmox_docker_network_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the proxmox_docker_network_create 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 proxmox_docker_network_create. 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.
proxmox_docker_network_create is provided by the MCP Proxmox Server MCP server (bsahane/mcp-proxmox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Proxmox Server, and thousands of servers like it.
This server
Across the catalogue