Create multiple QR codes in a single request (up to 50). Each item supports the same options as create_qr_code. The quota check is all-or-nothing: if the batch would exceed your plan limit, no QR codes are created. Ideal for generating QR codes for product catalogs, event lists, or batch operations.
AI agents use bulk_create_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 codes to create. Max 50 per request. |
Parameters from the server's own tool schema.
This tool creates and persists new QR code records, which is a write operation that modifies system state by adding new data. It is not destructive (deletion is handled by bulk_delete_qr_codes), not financial, and not execute (it generates codes rather than running arbitrary commands). The blast radius is low because QR code creation is benign and bounded by plan limits. The operation is reversible via deletion.
From the tool's definition Tool name contains 'create' and description states 'Create multiple QR codes in a single request'. The operation is reversible as indicated by the sibling tool 'bulk_delete_qr_codes' and the server description mentions 'update' functionality.
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
Create multiple QR codes in a single request (up to 50). Each item supports the same options as create_qr_code. The quota check is all-or-nothing: if the batch would exceed your plan limit, no QR codes are created. Ideal for generating QR codes for product catalogs, event lists, or batch operations. 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_create_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_create_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_create_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_create_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_create_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_create_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 →