Update multiple QR codes in a single request (up to 50). Change target URLs and/or labels. Items with non-existent short_id are reported as not_found without failing the whole batch.
AI agents use bulk_update_qr_codes to create or update resources in QR for Agent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QR for Agent environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
items | array | Yes | Array of QR code updates. Max 50 per request. |
Parameters from the server's own tool schema.
This tool creates reversible modifications to QR code metadata (target URLs, labels). It does not delete data (which would be Destructive), does not execute arbitrary code (which would be Execute), and is not financial in nature. The ability to update URLs could affect where QR codes redirect, but the operation itself is reversible—the target can be changed again.
From the tool's definition Tool description explicitly states 'Update multiple QR codes' and 'Change target URLs and/or labels', indicating modification of existing data. The phrase 'in a single request (up to 50)' confirms batch write operations.
Attacks that exploit this kind of access
Update multiple QR codes in a single request (up to 50). Change target URLs and/or labels. Items with non-existent short_id are reported as not_found without failing the whole batch. It is categorised as a Write tool in the QR for Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
bulk_update_qr_codes accepts 1 parameter: items. Required: items. 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_update_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_update_qr_codes is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the bulk_update_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_update_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_update_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 →