Drop a trigger
AI agents call db_drop_trigger 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.
The tool performs an irreversible deletion of a database trigger. Dropping a trigger cannot be undone without restoring from backup or replaying migrations. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone (delete, drop, purge, force-push).' The severity is high because accidental trigger removal could break critical database-dependent…
From the tool's definition Tool name contains 'drop' and description states 'Drop a trigger' - drop operations irreversibly remove database objects.
Attacks that exploit this kind of access
Drop a trigger. 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_trigger: 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_trigger 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_trigger 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_trigger. 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_trigger 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 →