List alert history (active + recently fired). Use to answer
AI agents call list_alerts to retrieve information from KVMFleet MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries alert history without side effects. It performs a read-only lookup operation. The server's read-only nature and the tool's listing/querying function place it squarely in the Read category with low severity, as misuse would only expose information rather than cause operational damage.
From the tool's definition Tool name 'list_alerts' and description 'List alert history' indicate retrieval of historical alert data with no modification capability. Server is explicitly described as 'Read-only MCP server' that 'allows AI assistants to query and monitor' systems.
Attacks that exploit this kind of access
List alert history (active + recently fired). Use to answer. It is categorised as a Read tool in the KVMFleet MCP Server MCP Server, which means it retrieves data without modifying state.
Register the KVMFleet MCP Server MCP server in PolicyLayer and add a rule for list_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 KVMFleet MCP Server. Nothing to install.
list_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 list_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 list_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.
list_alerts is provided by the KVMFleet MCP Server MCP server (kvmfleet/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 →