Create a QR code that redirects to the correct app store based on the device. iPhones go to the App Store, Android devices go to Google Play, and other devices go to the fallback URL. Provide at least one store URL.
AI agents use create_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 | — | Label for this QR code. |
format | string | — | Image format. |
ios_url | string | — | Apple App Store URL. |
logo_url | string | — | Logo URL or data URI. |
dot_style | string | — | Dot shape. |
frame_text | string | — | CTA text on frame (max 30 chars). |
android_url | string | — | Google Play Store URL. |
frame_color | string | — | Frame background color. |
frame_style | string | — | Frame style around QR. |
corner_style | string | — | Corner shape. |
fallback_url | string | — | Fallback URL for non-mobile devices. |
background_color | string | — | Hex color for background. |
Parameters from the server's own tool schema.
This tool generates QR code records that point to app store URLs. It is a create/write operation that produces new data artifacts but does not execute arbitrary code, modify existing records destructively, or involve financial transactions. The output is a QR code that can be edited or deleted later.
From the tool's definition Tool name 'create_app_store_qr' and description 'Create a QR code that redirects' — the tool creates new QR code data (a reversible write operation).
Risk signalsHigh parameter count (14 properties)
Attacks that exploit this kind of access
Create a QR code that redirects to the correct app store based on the device. iPhones go to the App Store, Android devices go to Google Play, and other devices go to the fallback URL. Provide at least one store URL. 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_app_store_qr accepts 12 parameters: label, format, ios_url, logo_url, dot_style, frame_text, android_url, frame_color, frame_style, corner_style, fallback_url, background_color. 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_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.
create_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 create_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 create_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.
create_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 →