Alias for get_events — the monitor's alerts are its edge-triggered events.
AI agents call get_alerts 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 tool merely queries and retrieves monitoring data (alerts/events) from the homelab dashboard. It performs no modifications, deletions, code execution, or financial operations. The read-only nature of the server and the retrieval-only semantics classify this as a Read operation with low severity, as misuse would only expose monitoring information without enabling harmful actions.
From the tool's definition Tool is described as an alias for `get_events`, and the server description explicitly states it is a 'read-only MCP server'. The tool retrieves alert/event data with no side effects.
Documented attack patterns abuse exactly the kind of access get_alerts 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_alerts:
{
"version": "1",
"default": "deny",
"tools": {
"get_alerts": {}
}
}get_alerts 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.
Alias for get_events — the monitor's alerts are its edge-triggered events. 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_alerts: 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_alerts 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_alerts 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_alerts. 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_alerts 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.