backup_config
Create a RouterOS backup file on the router.
This record as markdown: /tools/mcp-control-plane/backup-config.md
What backup_config does on Mcp Control Plane
AI agents use backup_config to create or update resources in Mcp Control Plane, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Control Plane environment.
Why backup_config is rated Medium
This tool creates (writes) a backup configuration file on a MikroTik RouterOS device. It is reversible—the backup file can be deleted or overwritten—so it does not meet the Destructive threshold. However, it modifies the router's filesystem by adding a new artifact.
From the tool's definition Tool creates a backup file on the router by calling 'backup_config' against RouterOS/MikroTik infrastructure. The description explicitly states 'Create a RouterOS backup file', which is a file creation operation.
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 Mcp Control Plane, 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 Mcp Control Plane, apply this rule, and every backup_config call is checked against it from then on.
Questions about backup_config
Create a RouterOS backup file on the router. It is categorised as a Write tool in the Mcp Control Plane MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Control Plane 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 Mcp Control Plane. 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 Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
This server
Across the catalogue