Update the app store URLs of an App Store QR code. Partial updates merge with existing data.
AI agents use update_app_store_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. |
ios_url | string | — | Apple App Store URL. |
short_id | string | Yes | The short ID of the App Store QR code to update. |
android_url | string | — | Google Play Store URL. |
fallback_url | string | — | Fallback URL. |
Parameters from the server's own tool schema.
This tool modifies existing QR code data (app store URLs) reversibly through a partial update/merge operation. It does not delete data (which would be Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read). The reversible nature of updates and ability to merge with existing data confirms Write category.
From the tool's definition Tool name 'update_app_store_qr' and description 'Update the app store URLs of an App Store QR code. Partial updates merge with existing data.' indicate modification of existing QR code data without deletion.
Attacks that exploit this kind of access
Update the app store URLs of an App Store 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_app_store_qr accepts 5 parameters: label, ios_url, short_id, android_url, fallback_url. 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_app_store_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_app_store_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_app_store_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_app_store_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_app_store_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 →