Remove stale lock files from the repository.
AI agents call unlock_repo to permanently remove resources in Restic — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing lock files is an irreversible deletion operation. Lock files serve a protective purpose (preventing concurrent access/modification), so forcibly removing them—even 'stale' ones—cannot be undone and could expose the repository to corruption if a lock was not actually stale. This qualifies as Destructive with medium severity since it affects repository integrity metadata rather than backup data directly.
From the tool's definition Remove stale lock files from the repository
Attacks that exploit this kind of access
Remove stale lock files from the repository. It is categorised as a Destructive tool in the Restic MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Restic MCP server in PolicyLayer and add a rule for unlock_repo: 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.
unlock_repo is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the unlock_repo 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 unlock_repo. 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.
unlock_repo 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 →