Delete multiple QR codes and their scan analytics in a single request (up to 50). Items with non-existent short_id are reported as not_found without failing the whole batch.
AI agents call bulk_delete_qr_codes to permanently remove resources in QR for Agent — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
short_ids | array | Yes | Array of short_id strings to delete. Max 50 per request. |
Parameters from the server's own tool schema.
This tool permanently removes QR codes and associated scan analytics. Deletion is inherently irreversible and destructive. While the blast radius is somewhat limited to QR code metadata rather than critical business data, the capacity to delete up to 50 items in a single batch request and the permanent loss of analytics tracking justifies 'high' severity.
From the tool's definition Delete multiple QR codes and their scan analytics in a single request — the word 'delete' combined with 'analytics' indicates irreversible removal of data that cannot be undone.
Attacks that exploit this kind of access
Delete multiple QR codes and their scan analytics in a single request (up to 50). Items with non-existent short_id are reported as not_found without failing the whole batch. It is categorised as a Destructive tool in the QR for Agent MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
bulk_delete_qr_codes accepts 1 parameter: short_ids. Required: short_ids. The full parameter table on this page comes from the server's own tool schema.
Register the QR for Agent MCP server in PolicyLayer and add a rule for bulk_delete_qr_codes: 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 QR for Agent. Nothing to install.
bulk_delete_qr_codes 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 bulk_delete_qr_codes 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 bulk_delete_qr_codes. 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.
bulk_delete_qr_codes is provided by the QR for Agent MCP server (qr-for-agent). 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 →