restore_database
Restore todos SQLite database from a local backup file.
This record as markdown: /tools/todos/restore-database.md
What restore_database does on Todos
AI agents call restore_database to permanently remove resources in Todos, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why restore_database is rated Critical
Restoring a database from backup overwrites all current data irreversibly. Any tasks, comments, artifacts, or other records added since the backup was taken would be permanently lost. This is an irreversible destructive operation with a critical blast radius for an AI agent managing task data.
From the tool's definition Restore todos SQLite database from a local backup file
Attacks that exploit this kind of access
The rule that runs restore_database safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Todos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For restore_database, this is the rule to start with:
restore_database is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Todos, apply this rule, and every restore_database call is checked against it from then on.
Questions about restore_database
Restore todos SQLite database from a local backup file. It is categorised as a Destructive tool in the Todos MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Todos MCP server in PolicyLayer and add a rule for restore_database: 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.
restore_database 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 restore_database 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 restore_database. 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.
restore_database 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.
More on Todos, and thousands of servers like it.
Across the catalogue