backup_config
Create a backup of the OPNsense configuration
This record as markdown: /tools/fakebizprez-opnsense-mcp-server/backup-config.md
What backup_config does on OPNsense MCP Server
AI agents use backup_config 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 backup_config is rated Medium
This tool creates/writes a backup file but does not destructively modify or delete existing data. While backups are generally defensive, the creation of a backup file in a firewall system could be misused to exfiltrate sensitive configuration data (passwords, VPN keys, firewall rules) if the backup is then retrieved.
From the tool's definition Tool name 'backup_config' and description 'Create a backup of the OPNsense configuration' indicate creation of a new backup artifact.
Attacks that exploit this kind of access
The rule that runs backup_config 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 backup_config, this is the rule to start with:
backup_config 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 backup_config call is checked against it from then on.
Questions about backup_config
Create a backup of the OPNsense configuration. 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 backup_config: 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.
backup_config 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 backup_config 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 backup_config. 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.
backup_config 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