AI agents call list_alert_history to retrieve information from Beszel without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns historical alert data from Beszel's monitoring system. It performs a read-only retrieval of existing alert records with no capability to modify, delete, execute, or create data. The blast radius of misuse is minimal—an agent could only access historical alert information that has already been triggered, presenting no operational risk.
From the tool's definition Tool name 'list_alert_history' and description 'List historical records of triggered alerts' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List historical records of triggered alerts in Beszel. It is categorised as a Read tool in the Beszel MCP Server, which means it retrieves data without modifying state.
Register the Beszel MCP server in PolicyLayer and add a rule for list_alert_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 Beszel. Nothing to install.
list_alert_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 list_alert_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 list_alert_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.
list_alert_history is provided by the Beszel MCP server (weeebdev/beszel-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 →