AI agents call opn_delete_alias 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 'delete' operation is inherently destructive—it removes configuration data irreversibly. Although the description is empty, the tool name and context (OPNsense firewall management, with complementary 'add' operations) make the destructive intent clear. Confidence is reduced slightly due to lack of explicit description, but the semantic weight of 'delete' in a firewall management context is strong.
From the tool's definition Tool name is 'opn_delete_alias'; the verb 'delete' indicates irreversible removal of data. Sibling tools include 'opn_add_alias', confirming that aliases are managed entities.
Documented attack patterns abuse exactly the kind of access opn_delete_alias 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_delete_alias:
{
"version": "1",
"default": "deny",
"hide": [
"opn_delete_alias"
]
}opn_delete_alias 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_delete_alias. 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_delete_alias: 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_delete_alias 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_delete_alias 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_delete_alias. 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_delete_alias 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.