Update the social media links of a Social QR code. Partial updates merge with existing data.
AI agents use update_social_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 | — | Update the label. |
github | string | — | GitHub URL. |
tiktok | string | — | TikTok URL. |
twitter | string | — | Twitter/X URL. |
website | string | — | Website URL. |
youtube | string | — | YouTube URL. |
facebook | string | — | Facebook URL. |
linkedin | string | — | LinkedIn URL. |
short_id | string | Yes | The short ID of the Social QR code to update. |
instagram | string | — | Instagram URL. |
Parameters from the server's own tool schema.
This tool modifies existing QR code data reversibly by updating social media links. It is a Write operation because it alters stored data without deleting it, and changes can be undone by further updates. The impact is low severity because QR codes are typically non-critical metadata with limited blast radius if misused by an agent.
From the tool's definition Tool name contains 'update' and description states 'Update the social media links'; 'Partial updates merge with existing data' confirms modification rather than creation or deletion.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
Update the social media links of a Social QR code. Partial updates merge with existing data. 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_social_qr accepts 10 parameters: label, github, tiktok, twitter, website, youtube, facebook, linkedin, short_id, instagram. 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_social_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_social_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_social_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_social_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_social_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 →