AI agents call memory_delete_event to permanently remove resources in Prometheus MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'delete' verb combined with 'event' in the tool name indicates irreversible data deletion. Even without a description, deletion operations are categorized as Destructive per the classification rules. Given the Prometheus/AWS context and the critical nature of monitoring data loss, this warrants critical severity.
From the tool's definition Tool name 'memory_delete_event' contains the verb 'delete', which indicates irreversible removal of data. The empty description prevents full clarification, but the naming convention strongly suggests a destructive operation on event memory or stored events.
Documented attack patterns abuse exactly the kind of access memory_delete_event gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Prometheus MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_delete_event:
{
"version": "1",
"default": "deny",
"hide": [
"memory_delete_event"
]
}memory_delete_event disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
memory_delete_event. It is categorised as a Destructive tool in the Prometheus MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Prometheus MCP Server MCP server in PolicyLayer and add a rule for memory_delete_event: 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 Prometheus MCP Server. Nothing to install.
memory_delete_event is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the memory_delete_event 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 memory_delete_event. 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.
memory_delete_event is provided by the Prometheus MCP Server MCP server (awslabs.prometheus-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Prometheus MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 Prometheus MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.