Resolve a fired alert — marks the underlying condition as handled.
AI agents use resolve_alert to create or update resources in KVMFleet MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your KVMFleet MCP Server environment.
The tool modifies alert state by marking a condition as handled. This is a reversible write operation (alerts can typically be re-opened or re-triggered), not a read operation (which would merely query alert status) and not destructive (the alert record is not deleted). While the server is described as 'read-only' overall, this tool performs a write action.
From the tool's definition Tool description states 'Resolve a fired alert — marks the underlying condition as handled.' This is a state-modifying operation that changes alert status from unresolved to resolved.
Attacks that exploit this kind of access
Resolve a fired alert — marks the underlying condition as handled. It is categorised as a Write tool in the KVMFleet MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the KVMFleet MCP Server MCP server in PolicyLayer and add a rule for resolve_alert: 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.
resolve_alert is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the resolve_alert 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 resolve_alert. 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.
resolve_alert 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 →