add_to_alias
Add an entry to a firewall alias
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.
Attacks that exploit this kind of access
The rule that runs add_to_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 add_to_alias, this is the rule to start with:
add_to_alias stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect OPNsense MCP Server, apply this rule, and every add_to_alias call is checked against it from then on.
Questions about add_to_alias
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.
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.
add_to_alias is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
This server
Across the catalogue