Create a QR code that opens a pre-filled email when scanned. The recipient, subject, body, CC, and BCC can all be pre-set.
AI agents use create_email_qr 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 |
|---|---|---|---|
cc | string | — | CC recipient(s). |
to | string | Yes | Recipient email address. |
bcc | string | — | BCC recipient(s). |
body | string | — | Email body text. |
label | string | — | Label for this QR code. |
format | string | — | Image format. |
subject | string | — | Email subject line. |
logo_url | string | — | Logo URL or data URI. |
dot_style | string | — | Dot shape. |
frame_text | string | — | CTA text on frame (max 30 chars). |
frame_color | string | — | Frame background color. |
frame_style | string | — | Frame style around QR. |
Parameters from the server's own tool schema.
Creating a QR code is a reversible write operation that produces new data. The tool does not execute arbitrary code, delete data irreversibly, move money, or read sensitive information—it simply encodes email metadata into a QR code format. The severity is low because misuse would at worst generate unwanted QR codes, which are easily ignored or deleted.
From the tool's definition Tool description states it "Create[s] a QR code" with pre-filled email parameters. This is a create operation that generates new data (the QR code artifact) without deletion or irreversible side effects.
Risk signalsAccepts raw HTML/template content (body) · High parameter count (16 properties)
Attacks that exploit this kind of access
Create a QR code that opens a pre-filled email when scanned. The recipient, subject, body, CC, and BCC can all be pre-set. 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.
create_email_qr accepts 12 parameters: cc, to, bcc, body, label, format, subject, logo_url, dot_style, frame_text, frame_color, frame_style. Required: to. 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 create_email_qr: 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.
create_email_qr 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 create_email_qr 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 create_email_qr. 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.
create_email_qr 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 →