restore_database

A destructive tool on the Mcpg MCP server.

SERVERMcpg SOURCEpypi:mcpg

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-devopam-mcpg/restore-database.md

WHAT IT DOES

What restore_database does on Mcpg

AI agents call restore_database to permanently remove resources in Mcpg, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why restore_database is rated Critical

A database restore operation overwrites the current state of the database with backup data, which is an irreversible destructive action that eliminates any data created or modified since the backup was taken. This has a critical blast radius as it can affect the entire database. Confidence is slightly reduced because the description is empty, but the tool name strongly implies this behavior.

From the tool's definition Tool name 'restore_database' — restoring a database typically overwrites existing data irreversibly, replacing current database contents with a prior snapshot or backup.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs restore_database safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, 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 Hidden

restore_database is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "restore_database"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcpg, apply this rule, and every restore_database call is checked against it from then on.

FAQ

Questions about restore_database

What does the restore_database tool do? +

restore_database is a destructive tool on the Mcpg MCP server. It is categorised as a Destructive tool in the Mcpg MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on restore_database? +

Register the Mcpg 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 Mcpg. Nothing to install.

What risk level is restore_database? +

restore_database is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit restore_database? +

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.

How do I block restore_database completely? +

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.

What MCP server provides restore_database? +

restore_database is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcpg, and thousands of servers like it.

This server

All 252 Mcpg tools → Critical-risk tools on this server →

Across the catalogue

delete_mysql_database on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →