AI agents call check_repo to retrieve information from Restic without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The check_repo tool performs validation and integrity checks on backup repository data without creating, modifying, or deleting any data. It is a diagnostic/query operation that reads repository state to verify consistency. This aligns with the Read category: retrieves or queries data with no side effects. Severity is low because integrity checks cannot damage data or cause business impact if misused by an agent.
From the tool's definition Tool name 'check_repo' and description 'Verify repository integrity by checking all data and metadata' indicate inspection/verification operations with no modifications.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Verify repository integrity by checking all data and metadata. It is categorised as a Read tool in the Restic MCP Server, which means it retrieves data without modifying state.
Register the Restic MCP server in PolicyLayer and add a rule for check_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.
check_repo is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_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 check_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.
check_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 →