adb_qemu_images
Manage QEMU disk images for virtual machines. List available images, create new qcow2/raw disk images, or delete existing ones. Images are stored in the DeepADB image directory.
This record as markdown: /tools/io-github-fullread-deepadb/adb-qemu-images.md
What adb_qemu_images does on Deepadb
AI agents call adb_qemu_images 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_qemu_images is rated Critical
The tool spans Write (create new images) and Destructive (delete existing images). Per the rules, the most severe applicable category wins. Deleting disk images is irreversible and could destroy VM data, making this Destructive. Severity is high because misuse could permanently wipe virtual machine disk images, potentially causing significant data loss.
From the tool's definition 'delete existing ones' — the tool can irreversibly delete QEMU disk images stored in the DeepADB image directory
Attacks that exploit this kind of access
The rule that runs adb_qemu_images 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_qemu_images, this is the rule to start with:
adb_qemu_images 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_qemu_images call is checked against it from then on.
Questions about adb_qemu_images
Manage QEMU disk images for virtual machines. List available images, create new qcow2/raw disk images, or delete existing ones. Images are stored in the DeepADB image directory. 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_qemu_images: 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_qemu_images 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_qemu_images 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_qemu_images. 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_qemu_images 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