order_node_certificate

Order/renew ACME certificate for a node.

SERVERProxmox MCP Server SOURCEgethosthewalrus/proxmox-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about order_node_certificate

What does the order_node_certificate tool do? +

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.

How do I enforce a policy on order_node_certificate? +

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.

What risk level is order_node_certificate? +

order_node_certificate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit order_node_certificate? +

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.

How do I block order_node_certificate completely? +

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.

What MCP server provides order_node_certificate? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Proxmox MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.