order_node_certificate
Order/renew ACME certificate for a node.
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/order-node-certificate.md
What order_node_certificate does on Proxmox MCP Server
AI agents invoke order_node_certificate to trigger actions in Proxmox MCP 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.
Why order_node_certificate is rated High
Ordering or renewing an ACME certificate triggers an external operation (communicating with an ACME CA, provisioning a new certificate, and updating the node's TLS configuration). This is not a simple read or write — it executes an external workflow with side effects on the node's certificate state. Misuse could disrupt node TLS/HTTPS access or exhaust ACME rate limits.
From the tool's definition Order/renew ACME certificate for a node
Attacks that exploit this kind of access
The rule that runs order_node_certificate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Proxmox MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For order_node_certificate, this is the rule to start with:
order_node_certificate stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Proxmox MCP Server, apply this rule, and every order_node_certificate call is checked against it from then on.
Questions about order_node_certificate
Order/renew ACME certificate for a node. It is categorised as a Execute tool in the Proxmox MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for order_node_certificate: 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 Proxmox MCP Server. Nothing to install.
order_node_certificate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the order_node_certificate 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 order_node_certificate. 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.
order_node_certificate is provided by the Proxmox MCP Server MCP server (gethosthewalrus/proxmox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Proxmox MCP Server, and thousands of servers like it.
Across the catalogue