list_alert_history
AI agents call list_alert_history to retrieve information from Beszel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool lists/retrieves alert history from the Beszel monitoring system. No side effects or state changes are implied. The empty description prevents higher confidence, but the naming pattern (list_*) and sibling tools (list_alerts, query_*) strongly suggest a read-only query operation. Blast radius is low—misuse would expose monitoring data but not cause system changes or financial impact.
From the tool's definition Tool name 'list_alert_history' and server context describing 'query system and container statistics, manage alerts, and monitor infrastructure' indicate this retrieves historical alert data without modification or execution.
Attacks that exploit this kind of access
list_alert_history. It is categorised as a Read tool in the Beszel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Beszel MCP Server 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 MCP Server. 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 MCP server (red5d/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 →