Update the contact details of a vCard QR code. Only works on QR codes created with type='vcard'. Partial updates merge with existing data. Note: updating vCard data changes the QR image content.
AI agents use update_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 | — | Update the label. |
phone | string | — | Phone number. |
title | string | — | Job title. |
address | string | — | Street address. |
short_id | string | Yes | The short ID of the vCard QR code to update. |
last_name | string | — | Contact last name. |
first_name | string | — | Contact first name. |
organization | string | — | Company or organization. |
Parameters from the server's own tool schema.
This tool creates or modifies data reversibly by updating vCard contact details within a QR code. While it changes the QR image content, the operation is non-destructive and can be reversed by updating again with different values. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or move money (would be Financial).
From the tool's definition Tool description states "Update the contact details of a vCard QR code" and "updating vCard data changes the QR image content." The action is reversible modification of existing data (partial updates merge with existing data).
Risk signalsAccepts URL/endpoint input (url) · High parameter count (11 properties)
Attacks that exploit this kind of access
Update the contact details of a vCard QR code. Only works on QR codes created with type='vcard'. Partial updates merge with existing data. Note: updating vCard data changes the QR image content. 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.
update_vcard_qr accepts 11 parameters: url, note, email, label, phone, title, address, short_id, last_name, first_name, organization. Required: short_id. 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 update_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.
update_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 update_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 update_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.
update_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 →