Charted time-series the dashboard graphs over range: timestamps + aligned arrays for GPU util/VRAM/power/temp and host CPU/RAM/load/temp. Use for trends.
AI agents call get_history to retrieve information from HomeLab Monitor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure data retrieval operation that queries historical metrics from the homelab dashboard. It has no side effects, cannot modify or delete data, and does not execute code or trigger external operations. The read-only nature of the server and the passive query semantics clearly indicate the Read category. Severity is low because exposure of monitoring data poses minimal risk.
From the tool's definition Tool name 'get_history' and description indicate retrieval of time-series data ('Charted time-series the dashboard graphs over `range`'). No modification, deletion, or execution of external operations occurs.
Documented attack patterns abuse exactly the kind of access get_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and HomeLab Monitor, and nothing reaches the server without passing your rules. This is the rule we recommend for get_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_history": {}
}
}get_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Charted time-series the dashboard graphs over range: timestamps + aligned arrays for GPU util/VRAM/power/temp and host CPU/RAM/load/temp. Use for trends. It is categorised as a Read tool in the HomeLab Monitor MCP Server, which means it retrieves data without modifying state.
Register the HomeLab Monitor MCP server in PolicyLayer and add a rule for get_history: 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 Monitor. Nothing to install.
get_history 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_history 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_history. 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_history is provided by the HomeLab Monitor MCP server (sikamikanikobg/homelab-monitor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 HomeLab Monitor tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 HomeLab Monitor tools catalogued and risk-classified — across an index of 42,500+ MCP servers.