Critical Risk →

haproxy_action_delete

Delete an HAProxy action

How to control haproxy_action_delete ↓

AI agents call haproxy_action_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.

Critical Risk

HAProxy actions control load balancing, SSL/TLS termination, routing, and traffic shaping. Deleting an action could disrupt critical network services, interrupt traffic flow, or disable security features.

From the tool's definition Tool name explicitly includes 'delete' and description states 'Delete an HAProxy action'. The action of deleting HAProxy configurations is irreversible and cannot be undone.

Documented attack patterns abuse exactly the kind of access haproxy_action_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 haproxy_action_delete:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "haproxy_action_delete"
  ]
}

haproxy_action_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register OPNSense MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the haproxy_action_delete tool do? +

Delete an HAProxy action. 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.

How do I enforce a policy on haproxy_action_delete? +

Register the OPNSense MCP Server MCP server in PolicyLayer and add a rule for haproxy_action_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.

What risk level is haproxy_action_delete? +

haproxy_action_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit haproxy_action_delete? +

Yes. Add a rate_limit block to the haproxy_action_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.

How do I block haproxy_action_delete completely? +

Set action: deny in the PolicyLayer policy for haproxy_action_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.

What MCP server provides haproxy_action_delete? +

haproxy_action_delete 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.

Enforce policy on every OPNSense MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.