backup
Backup: config files, system state snapshots, restore, verify integrity, list backups
This record as markdown: /tools/defense/backup.md
What backup does on Defense
AI agents use backup to create or update resources in Defense, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Defense environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
tag | string | — | Tag for this backup set |
files | string | — | Comma-separated file paths to back up |
limit | number | — | Maximum number of results |
action | string | Yes | Backup management action |
filter | string | — | Filter by filename pattern |
dry_run | boolean | — | Preview without executing |
sort_by | string | — | Sort order |
output_dir | string | — | Directory to save snapshot files |
backup_path | string | — | Path to the backup file |
include_users | boolean | — | Include user/group information |
original_path | string | — | Original file path to restore to |
check_integrity | boolean | — | Compute and verify SHA256 checksums |
Parameters from the server's own tool schema.
Why backup is rated Medium
The tool performs multiple operations. Listing and integrity verification are Read-level, but creating snapshots and restoring system state are Write/Execute-level actions. Restore in particular can overwrite live system configuration, making misuse high-severity.
From the tool's definition 'config files, system state snapshots, restore, verify integrity, list backups' — covers both reading/listing and writing backup data, plus restore operations that overwrite system state
Risk signalsHigh parameter count (16 properties)
Attacks that exploit this kind of access
The rule that runs backup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Defense, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For backup, this is the rule to start with:
backup 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 Defense, apply this rule, and every backup call is checked against it from then on.
Questions about backup
Backup: config files, system state snapshots, restore, verify integrity, list backups. It is categorised as a Write tool in the Defense MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
backup accepts 12 parameters: tag, files, limit, action, filter, dry_run, sort_by, output_dir, backup_path, include_users, original_path, check_integrity. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the Defense MCP server in PolicyLayer and add a rule for backup: 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 Defense. Nothing to install.
backup 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 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. 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 is provided by the Defense MCP server (defense-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Defense, and thousands of servers like it.
This server
Across the catalogue