restore_local_backup · Todos MCP: Risk & Policy

WHAT IT DOES

What restore_local_backup does on Todos

AI agents use restore_local_backup to create or update resources in Todos — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todos environment.

WHY IT NEEDS A POLICY

Why restore_local_backup needs a policy

restore_local_backup performs reversible data modification—it restores previously backed-up data to the system. While it has a safe dry-run mode by default, the apply action creates/overwrites task data. This is Write rather than Destructive because restore operations are generally reversible (can be restored again from another backup or undone), and the tool is designed for recovery rather than permanent deletion.

From the tool's definition Tool description states it can "apply a local backup restore" and "write" data, with dry-run as default but actual restoration capability present. The verb "restore" and "apply" indicate data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

restore_local_backup Rate-limited

restore_local_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "restore_local_backup": {
      "limits": [
        {
          "counter": "restore_local_backup_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Todos, so you can run agents against it safely.

FAQ

Questions about restore_local_backup

What does the restore_local_backup tool do? +

Dry-run or apply a local backup restore. Dry-run is the default and reports conflicts before writing. It is categorised as a Write tool in the Todos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on restore_local_backup? +

Register the Todos MCP server in PolicyLayer and add a rule for restore_local_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 Todos. Nothing to install.

What risk level is restore_local_backup? +

restore_local_backup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit restore_local_backup? +

Yes. Add a rate_limit block to the restore_local_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.

How do I block restore_local_backup completely? +

Set action: deny in the PolicyLayer policy for restore_local_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.

What MCP server provides restore_local_backup? +

restore_local_backup is provided by the Todos MCP server (@hasna/todos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.