AI agents call prometheus_snapshot to retrieve information from Homelab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves current system and infrastructure metrics for informational/observational purposes. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an AI agent querying metrics cannot damage the homelab, trigger actions, or affect system state. This is classified as Read severity low.
From the tool's definition Tool provides a snapshot of monitoring metrics (CPU%, RAM, disk usage, network throughput, container count, scrape target health). It queries and retrieves data with no modifying operations; metrics snapshot functionality is inherently read-only.
Attacks that exploit this kind of access
Quick homelab metrics snapshot: CPU%, RAM, disk usage, network throughput, container count, and scrape target health. It is categorised as a Read tool in the Homelab MCP Server, which means it retrieves data without modifying state.
Register the Homelab MCP server in PolicyLayer and add a rule for prometheus_snapshot: 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 Homelab. Nothing to install.
prometheus_snapshot 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 prometheus_snapshot 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 prometheus_snapshot. 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.
prometheus_snapshot is provided by the Homelab MCP server (nainounen/homelab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →