Recent edge-triggered events over range (OOM kills, threshold crossings), each with a blame line where one can be attributed, plus derived insights.
AI agents call get_events 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.
The tool queries historical event data and returns derived insights. There are no side effects, no data modification, no code execution, and no irreversible actions. This is a pure retrieval operation fitting the Read category. Low severity because unauthorized access to homelab monitoring data poses minimal risk—it reveals system state but enables no harmful actions.
From the tool's definition Tool retrieves 'recent edge-triggered events' (OOM kills, threshold crossings) with insights; no modification, deletion, or execution described. Consistent with sibling tools (all prefixed 'get_'), and server is explicitly 'read-only MCP server'.
Documented attack patterns abuse exactly the kind of access get_events 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_events:
{
"version": "1",
"default": "deny",
"tools": {
"get_events": {}
}
}get_events 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.
Recent edge-triggered events over range (OOM kills, threshold crossings), each with a blame line where one can be attributed, plus derived insights. 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_events: 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_events 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_events 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_events. 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_events 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.