db_remove_database
AI agents call db_remove_database to permanently remove resources in Custom MCP Database Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although the description is empty (lowering confidence slightly from 1.0), the tool name unambiguously describes a destructive operation. 'Remove' in the context of database management typically means deletion. Destructive takes priority over Execute because the action cannot be undone.
From the tool's definition Tool name 'db_remove_database' clearly indicates permanent removal of a database configuration or data store. Given the server's purpose of managing database connections for AI agents, this tool allows irreversible deletion of database resources.
Attacks that exploit this kind of access
db_remove_database. It is categorised as a Destructive tool in the Custom MCP Database Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Custom MCP Database Server MCP server in PolicyLayer and add a rule for db_remove_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 Custom MCP Database Server. Nothing to install.
db_remove_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 db_remove_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 db_remove_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.
db_remove_database is provided by the Custom MCP Database Server MCP server (renanlido/custom-mcp-database). 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 →