AI agents call opn_haproxy_delete 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.
Although the description is empty (lowering confidence from 0.95 to 0.85), the tool name itself clearly contains 'delete', which is a destructive operation. HAProxy is a critical load balancer; deleting configurations or rules would be irreversible and could cause service outages. This exceeds the threshold for Write (which is reversible) and qualifies as Destructive.
From the tool's definition Tool name 'opn_haproxy_delete' indicates deletion of HAProxy configuration or resources. The 'delete' verb combined with HAProxy management context indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access opn_haproxy_delete 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 opn_haproxy_delete:
{
"version": "1",
"default": "deny",
"hide": [
"opn_haproxy_delete"
]
}opn_haproxy_delete 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.
opn_haproxy_delete. 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 opn_haproxy_delete: 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.
opn_haproxy_delete 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 opn_haproxy_delete 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 opn_haproxy_delete. 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.
opn_haproxy_delete is provided by the OPNsense MCP Server MCP server (lucamarien/opnsense-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OPNsense 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.
81 OPNsense MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.