Create a QR code that encodes a contact card (vCard). When scanned by a phone camera, it prompts the user to save the contact. Supports all standard vCard fields and custom QR styling.
AI agents use create_vcard_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 |
|---|---|---|---|
url | string | — | Website URL. |
note | string | — | Additional notes. |
email | string | — | Email address. |
label | string | — | Label for this QR code. |
phone | string | — | Phone number. |
title | string | — | Job title. |
format | string | — | Image format. |
address | string | — | Street address. |
logo_url | string | — | Logo URL or data URI. |
dot_style | string | — | Dot shape. |
last_name | string | Yes | Contact last name. |
first_name | string | Yes | Contact first name. |
Parameters from the server's own tool schema.
This tool creates new QR code records containing vCard data. Creation of data without irreversible side effects or external state changes (no deletion, no financial impact, no code execution on remote systems) qualifies as Write. The low severity reflects minimal blast radius: a malicious agent could create many QR codes, but this causes no data loss, financial harm, or system compromise.
From the tool's definition Tool description states 'Create a QR code' and 'encodes a contact card (vCard)', indicating data creation. The vCard content is user-supplied and reversible—QR codes can be deleted or updated without permanent damage.
Risk signalsAccepts URL/endpoint input (url) · High parameter count (20 properties)
Attacks that exploit this kind of access
Create a QR code that encodes a contact card (vCard). When scanned by a phone camera, it prompts the user to save the contact. Supports all standard vCard fields and custom QR styling. 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_vcard_qr accepts 12 parameters: url, note, email, label, phone, title, format, address, logo_url, dot_style, last_name, first_name. Required: last_name, first_name. 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_vcard_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_vcard_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_vcard_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_vcard_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_vcard_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 →