dump_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/dump-database.md

WHAT IT DOES

What dump_database does on Mcpg

AI agents call dump_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 dump_database is rated Critical

While a database dump is technically a Read operation (exporting data), the name 'dump_database' on a production PostgreSQL server could also imply destructive behavior (e.g., dropping/purging data). Given the empty description and the ambiguity, the most severe plausible interpretation is chosen. However, if this is purely an export operation, it would be Read with high data-exfiltration risk.

From the tool's definition Tool name 'dump_database' — description is empty and uninformative, lowering confidence. However, 'dump_database' on a production-grade PostgreSQL MCP server most commonly refers to a full database export/dump operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dump_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 dump_database, this is the rule to start with:

dump_database Hidden

dump_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": [
    "dump_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 dump_database call is checked against it from then on.

FAQ

Questions about dump_database

What does the dump_database tool do? +

dump_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 dump_database? +

Register the Mcpg MCP server in PolicyLayer and add a rule for dump_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 dump_database? +

dump_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 dump_database? +

Yes. Add a rate_limit block to the dump_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 dump_database completely? +

Set action: deny in the PolicyLayer policy for dump_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 dump_database? +

dump_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 →