Create a QR code that initiates a phone call when scanned. The phone number is encoded directly in the QR code.
AI agents use create_phone_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 |
|---|---|---|---|
label | string | — | Label for this QR code. |
format | string | — | Image format. |
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. |
corner_style | string | — | Corner shape. |
phone_number | string | Yes | Phone number to call. |
background_color | string | — | Hex color for background. |
foreground_color | string | — | Hex color for dots. |
frame_text_color | string | — | Frame text color. |
Parameters from the server's own tool schema.
This tool creates a new QR code artifact with encoded phone call metadata. It is a reversible write operation (QR codes can be deleted or replaced). There is no destructive action, code execution, financial transaction, or irreversible side effect. The severity is low because misuse would result in creation of unwanted QR codes that could be deleted, with minimal blast radius.
From the tool's definition Tool name 'create_phone_qr' and description 'Create a QR code that initiates a phone call when scanned' indicate data creation. The phone number is 'encoded directly in the QR code', meaning the tool generates and stores new QR code data.
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
Create a QR code that initiates a phone call when scanned. The phone number is encoded directly in the QR code. 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_phone_qr accepts 12 parameters: label, format, logo_url, dot_style, frame_text, frame_color, frame_style, corner_style, phone_number, background_color, foreground_color, frame_text_color. Required: phone_number. 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_phone_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_phone_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_phone_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_phone_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_phone_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 →