AI agents call monit_delete_alert to permanently remove resources in OPNSense MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion operation on alert recipient configuration. While the blast radius is limited compared to critical system changes, deletion of monitoring alerts could disable important security notifications, potentially allowing breaches to go undetected. This meets the Destructive category definition as the action cannot be undone without manual reconfiguration.
From the tool's definition Tool name contains 'delete' and description states 'Delete a Monit alert recipient' - this irreversibly removes a monitoring alert configuration.
Documented attack patterns abuse exactly the kind of access monit_delete_alert gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OPNSense MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for monit_delete_alert:
{
"version": "1",
"default": "deny",
"hide": [
"monit_delete_alert"
]
}monit_delete_alert 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.
Delete a Monit alert recipient. It is categorised as a Destructive tool in the OPNSense MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OPNSense MCP Server MCP server in PolicyLayer and add a rule for monit_delete_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 OPNSense MCP Server. Nothing to install.
monit_delete_alert 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 monit_delete_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 monit_delete_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.
monit_delete_alert is provided by the OPNSense MCP Server MCP server (vespo92/opnsensemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 196 OPNSense MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
196 OPNSense MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.