get_metric_server
Get metric server configuration.
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/get-metric-server.md
What get_metric_server does on Proxmox MCP Server
AI agents call get_metric_server to retrieve information from Proxmox MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_metric_server is rated Low
This tool retrieves existing metric server configuration without modifying, executing code, deleting data, or moving money. The blast radius of misuse is minimal—an attacker gains only informational access to monitoring infrastructure settings. Confidence is high because the description unambiguously describes a read-only query operation.
From the tool's definition Tool name 'get_metric_server' and description 'Get metric server configuration' indicate a retrieval operation with no side effects. The verb 'get' and action of reading configuration data align with Read category semantics.
Attacks that exploit this kind of access
The rule that runs get_metric_server 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 get_metric_server, this is the rule to start with:
get_metric_server 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 Proxmox MCP Server, apply this rule, and every get_metric_server call is checked against it from then on.
Questions about get_metric_server
Get metric server configuration. It is categorised as a Read tool in the Proxmox MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for get_metric_server: 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.
get_metric_server 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 get_metric_server 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 get_metric_server. 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.
get_metric_server 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.
This server
Across the catalogue