Delete a database
AI agents call delete_database to permanently remove resources in Rockfish MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes an entire database and all its contents. Deleting a database is a destructive action with high blast radius in an ML operations context—loss of training data, model artifacts, or project data could halt workflows and cause significant operational damage. While not directly financial, the impact is severe enough to warrant 'high' severity classification.
From the tool's definition Tool name is 'delete_database' with description 'Delete a database'. The verb 'delete' combined with 'database' (a persistent data store) indicates irreversible removal of data that cannot be undone.
Attacks that exploit this kind of access
Delete a database. It is categorised as a Destructive tool in the Rockfish MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Rockfish MCP Server MCP server in PolicyLayer and add a rule for delete_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 Rockfish MCP Server. Nothing to install.
delete_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 delete_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 delete_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.
delete_database is provided by the Rockfish MCP Server MCP server (wolfdancer/rockfish-mcp). 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 →