validate_clusters
Validate connectivity to all clusters.
This record as markdown: /tools/bsahane-mcp-proxmox/validate-clusters.md
What validate_clusters does on MCP Proxmox Server
AI agents call validate_clusters 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 validate_clusters is rated Low
Validation/connectivity checks are read-only operations that test reachability without modifying any data or state. The tool queries cluster status to confirm connections, producing no side effects.
From the tool's definition Validate connectivity to all clusters
Attacks that exploit this kind of access
The rule that runs validate_clusters 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 validate_clusters, this is the rule to start with:
validate_clusters is read-only, so it stays allowed. 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 validate_clusters call is checked against it from then on.
Questions about validate_clusters
Validate connectivity to all clusters. It is categorised as a Read tool in the MCP Proxmox Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Proxmox Server MCP server in PolicyLayer and add a rule for validate_clusters: 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.
validate_clusters is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the validate_clusters 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 validate_clusters. 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.
validate_clusters 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