AI agents use create_backup to create or update resources in Restic — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Restic environment.
This tool creates new backup data in the repository. It is a Write operation as it adds new snapshot data without deleting or overwriting existing data. Misuse could cause storage bloat or back up sensitive/unintended paths, hence medium severity.
From the tool's definition Create a new backup of the specified paths
Attacks that exploit this kind of access
Create a new backup of the specified paths. It is categorised as a Write tool in the Restic MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Restic MCP server in PolicyLayer and add a rule for create_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 Restic. Nothing to install.
create_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 create_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 create_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.
create_backup is provided by the Restic MCP server (mohsenil85/restic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →