Deregister a database from NDB which means the database will no longer be managed by NDB. This does not delete the database from the dbserver, but removes it from NDB management. Use delete=true to also delete the database from the dbserver.
AI agents call deregister_database to permanently remove resources in NDB MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs irreversible operations: deregistering a database from NDB management cannot be undone, and the delete=true variant permanently destroys the database. Even without the delete flag, deregistration is a destructive state change that severs management oversight. The blast radius is critical—an AI agent misusing this could cause permanent loss of database visibility or data.
From the tool's definition Tool description states it will "deregister a database from NDB" and explicitly offers a delete parameter "Use delete=true to also delete the database from the dbserver." The deregister operation itself removes management but is irreversible; the delete…
Attacks that exploit this kind of access
Deregister a database from NDB which means the database will no longer be managed by NDB. This does not delete the database from the dbserver, but removes it from NDB management. Use delete=true to also delete the database from the dbserver. It is categorised as a Destructive tool in the NDB MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the NDB MCP Server MCP server in PolicyLayer and add a rule for deregister_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 NDB MCP Server. Nothing to install.
deregister_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 deregister_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 deregister_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.
deregister_database is provided by the NDB MCP Server MCP server (rouxton/ndb-mcp-server). 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 →