add_to_alias

Add an entry to a firewall alias

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

This record as markdown: /tools/fakebizprez-opnsense-mcp-server/add-to-alias.md

What add_to_alias does on OPNsense MCP Server

AI agents use add_to_alias to create or update resources in OPNsense MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OPNsense MCP Server environment.

Why add_to_alias is rated Medium

The tool modifies firewall alias configuration—a core security control—but the change is reversible through deletion. This qualifies as Write rather than Destructive. Severity is high because firewall aliases are used in rule definitions and network policies; a misconfigured alias via AI misuse could redirect traffic unexpectedly or create security gaps, affecting network access control.

From the tool's definition Tool name 'add_to_alias' and description 'Add an entry to a firewall alias' indicate modification of firewall configuration data.

Questions about add_to_alias

What does the add_to_alias tool do? +

Add an entry to a firewall alias. It is categorised as a Write tool in the OPNsense MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_to_alias? +

Register the OPNsense MCP Server MCP server in PolicyLayer and add a rule for add_to_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 add_to_alias? +

add_to_alias is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_to_alias? +

Yes. Add a rate_limit block to the add_to_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 add_to_alias completely? +

Set action: deny in the PolicyLayer policy for add_to_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 add_to_alias? +

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