Restore database from backup
AI agents call restore_database to permanently remove resources in PostgreSQL MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
A database restore is a destructive, irreversible operation at the broadest possible blast radius: it replaces all tables, rows, schemas, and configurations in the target database with the backup contents. Any data written after the backup point is permanently lost. This qualifies as Destructive with critical severity because misuse could wipe an entire production database.
From the tool's definition 'Restore database from backup' — restoring a database overwrites all existing data irreversibly, replacing the current state of the entire database with the backup contents.
Attacks that exploit this kind of access
Restore database from backup. It is categorised as a Destructive tool in the PostgreSQL MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PostgreSQL MCP Server 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 PostgreSQL MCP Server. 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 PostgreSQL MCP Server MCP server (reckersai/mcpg). 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 →