list_metric_servers

List configured metric servers (InfluxDB, Graphite).

SERVERProxmox MCP Server SOURCEgethosthewalrus/proxmox-mcp

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/gethosthewalrus-proxmox-mcp/list-metric-servers.md

WHAT IT DOES

What list_metric_servers does on Proxmox MCP Server

AI agents call list_metric_servers 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.

RISK

Why list_metric_servers is rated Low

This tool only retrieves and lists existing metric server configurations. It performs no side effects, creates no resources, executes no operations, and modifies no data. It is a simple informational lookup, making it a Read category tool with low severity since misuse would only expose non-sensitive configuration details about monitoring infrastructure.

From the tool's definition Tool name 'list_metric_servers' and description 'List configured metric servers (InfluxDB, Graphite)' indicate a read-only query operation that retrieves configuration information without modifying or executing any infrastructure changes.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_metric_servers 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 list_metric_servers, this is the rule to start with:

list_metric_servers Allowed

list_metric_servers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_metric_servers": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Proxmox MCP Server, apply this rule, and every list_metric_servers call is checked against it from then on.

FAQ

Questions about list_metric_servers

What does the list_metric_servers tool do? +

List configured metric servers (InfluxDB, Graphite). It is categorised as a Read tool in the Proxmox MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_metric_servers? +

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

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

Can I rate-limit list_metric_servers? +

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

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

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

KEEP EXPLORING

More on Proxmox MCP Server, and thousands of servers like it.

This server

All 286 Proxmox MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →