Change where an existing QR code redirects to. This is the key 'dynamic link' feature: the QR image stays the same, but scanning it will now go to the new URL. Ideal for updating campaigns, fixing broken links, or A/B testing.
AI agents use update_qr_destination 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 | — | Optionally update the label too. |
short_id | string | Yes | The short ID of the QR code to update. |
expires_at | object | — | ISO 8601 expiration date. Set to null to remove expiration. |
target_url | string | Yes | The new destination URL. |
scheduled_at | object | — | ISO 8601 activation date for scheduled_url. Set to null to cancel. |
scheduled_url | object | — | Scheduled replacement URL. Set to null to cancel. |
gtm_container_id | object | — | Google Tag Manager container ID. Set to null to remove GTM tracking. |
Parameters from the server's own tool schema.
This tool modifies existing QR code data (the redirect URL) but does not delete, destroy, or irreversibly alter anything. The change can be undone by updating the destination again. While it could be misused to redirect users to malicious sites, that depends entirely on the target URL specified by the operator, not on the tool itself.
From the tool's definition Tool description states 'Change where an existing QR code redirects to' and 'update campaigns, fixing broken links'. The verb 'update' and the reversible nature of changing a redirect destination confirm this is a Write operation.
Attacks that exploit this kind of access
Change where an existing QR code redirects to. This is the key 'dynamic link' feature: the QR image stays the same, but scanning it will now go to the new URL. Ideal for updating campaigns, fixing broken links, or A/B testing. 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_qr_destination accepts 7 parameters: label, short_id, expires_at, target_url, scheduled_at, scheduled_url, gtm_container_id. Required: short_id, target_url. 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_qr_destination: 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_qr_destination 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_qr_destination 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_qr_destination. 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_qr_destination 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 →