proxmox_node_status

A read tool on the MCP Proxmox MCP server.

SERVERMCP Proxmox Server SOURCEbsahane/mcp-proxmox
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/bsahane-mcp-proxmox/proxmox-node-status.md

What proxmox_node_status does on MCP Proxmox Server

AI agents call proxmox_node_status to retrieve information from MCP Proxmox Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why proxmox_node_status is rated Low

Although the description is empty, the tool name and context strongly suggest this retrieves status/monitoring data rather than executing operations or modifying infrastructure. This is a Read operation. Severity is medium because unauthorized access to Proxmox node status could reveal infrastructure topology and operational details useful for attack planning, though it causes no direct damage.

From the tool's definition Tool name 'proxmox_node_status' indicates retrieval of node status information. Within a Proxmox infrastructure management context, this retrieves operational metrics and state data about cluster nodes without modifying resources.

Questions about proxmox_node_status

What does the proxmox_node_status tool do? +

proxmox_node_status is a read tool on the MCP Proxmox Server MCP server. It is categorised as a Read tool in the MCP Proxmox Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on proxmox_node_status? +

Register the MCP Proxmox Server MCP server in PolicyLayer and add a rule for proxmox_node_status: 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.

What risk level is proxmox_node_status? +

proxmox_node_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit proxmox_node_status? +

Yes. Add a rate_limit block to the proxmox_node_status 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 proxmox_node_status completely? +

Set action: deny in the PolicyLayer policy for proxmox_node_status. 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 proxmox_node_status? +

proxmox_node_status 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.

// 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 MCP Proxmox 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.