delete_from_alias
Delete an entry from a firewall alias
This record as markdown: /tools/fakebizprez-opnsense-mcp-server/delete-from-alias.md
What delete_from_alias does on OPNsense MCP Server
AI agents call delete_from_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.
Why delete_from_alias is rated Critical
Deleting alias entries is a destructive operation that cannot be undone without manual restoration or backups. Alias entries are often critical to firewall rule functionality—removing them could break security policies or network access controls. This is more severe than Write (which is reversible) and represents a permanent modification to firewall configuration.
From the tool's definition Tool name is 'delete_from_alias' with description 'Delete an entry from a firewall alias'. The verb 'delete' combined with removal of alias entries indicates irreversible deletion of firewall configuration data.
Attacks that exploit this kind of access
The rule that runs delete_from_alias safely
PolicyLayer is an MCP gateway: it sits between your AI agents and OPNsense MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_from_alias, this is the rule to start with:
delete_from_alias is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect OPNsense MCP Server, apply this rule, and every delete_from_alias call is checked against it from then on.
Questions about delete_from_alias
Delete an entry from a firewall 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 delete_from_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.
delete_from_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 delete_from_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 delete_from_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.
delete_from_alias is provided by the OPNsense MCP Server MCP server (fakebizprez/opnsense-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on OPNsense MCP Server, and thousands of servers like it.
Across the catalogue