Drop a sequence
AI agents call db_drop_sequence to permanently remove resources in Database MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Dropping a sequence permanently removes a database object and cannot be undone without restore from backup. This is an irreversible destructive operation on database schema. The blast radius includes potential application failures if code depends on this sequence for ID generation, and data integrity issues if the sequence is referenced by dependent objects.
From the tool's definition Tool name is 'db_drop_sequence' with description 'Drop a sequence'. The verb 'drop' in database contexts means irreversible deletion of a schema object.
Attacks that exploit this kind of access
Drop a sequence. It is categorised as a Destructive tool in the Database MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Database MCP Server MCP server in PolicyLayer and add a rule for db_drop_sequence: 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 Database MCP Server. Nothing to install.
db_drop_sequence 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_drop_sequence 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_drop_sequence. 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_drop_sequence is provided by the Database MCP Server MCP server (roilanrodriguez55/database-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 →