delete_from_alias

Delete an entry from a firewall alias

SERVEROPNsense MCP Server SOURCEfakebizprez/opnsense-mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about delete_from_alias

What does the delete_from_alias tool do? +

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.

How do I enforce a policy on delete_from_alias? +

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.

What risk level is delete_from_alias? +

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.

Can I rate-limit delete_from_alias? +

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.

How do I block delete_from_alias completely? +

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.

What MCP server provides delete_from_alias? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of OPNsense MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.