adb_result_drop
Delete a stored result handle, or clear all handles in this session. Either provide both
This record as markdown: /tools/io-github-fullread-deepadb/adb-result-drop.md
What adb_result_drop does on Deepadb
AI agents call adb_result_drop to permanently remove resources in Deepadb, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why adb_result_drop is rated Critical
This tool irreversibly deletes stored result handles. While the blast radius is constrained to session state (not production data), deletion is permanent and cannot be undone. Destructive operations that clear or remove data without recovery options warrant the 'Destructive' category. Severity is high rather than critical because the damage is scoped to session results, not persistent or cross-user systems.
From the tool's definition The tool name contains 'drop' and the description states 'Delete a stored result handle' — 'delete' is an explicit destructive operation keyword.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs adb_result_drop safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deepadb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_result_drop, this is the rule to start with:
adb_result_drop is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_result_drop call is checked against it from then on.
Questions about adb_result_drop
Delete a stored result handle, or clear all handles in this session. Either provide both. It is categorised as a Destructive tool in the Deepadb MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_result_drop: 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 Deepadb. Nothing to install.
adb_result_drop 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 adb_result_drop 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 adb_result_drop. 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.
adb_result_drop is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deepadb, and thousands of servers like it.
Across the catalogue