Create a QR code that adds a calendar event when scanned. Encodes a standard iCalendar VEVENT that calendar apps can import.
AI agents use create_event_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 |
|---|---|---|---|
end | string | Yes | Event end date-time in ISO 8601 format. |
label | string | — | Label for this QR code. |
start | string | Yes | Event start date-time in ISO 8601 format (e.g. 2026-03-15T09:00:00Z). |
format | string | — | Image format. |
summary | string | Yes | Event title/summary. |
location | string | — | Event location. |
logo_url | string | — | Logo URL or data URI. |
dot_style | string | — | Dot shape. |
frame_text | string | — | CTA text on frame (max 30 chars). |
description | string | — | Event description. |
frame_color | string | — | Frame background color. |
frame_style | string | — | Frame style around QR. |
Parameters from the server's own tool schema.
This tool creates and encodes new calendar event data into a QR code format. It is reversible (the QR code can be deleted or replaced) and has no destructive, financial, or execution side effects. It falls squarely in the Write category: a creation operation that adds new data to the system.
From the tool's definition Tool name and description explicitly state 'Create a QR code' and 'Encodes a standard iCalendar VEVENT'. The operation creates new data (a QR code and its encoded calendar event) without deleting or modifying existing data, and does not execute arbitrary code…
Risk signalsHigh parameter count (16 properties)
Attacks that exploit this kind of access
Create a QR code that adds a calendar event when scanned. Encodes a standard iCalendar VEVENT that calendar apps can import. 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_event_qr accepts 12 parameters: end, label, start, format, summary, location, logo_url, dot_style, frame_text, description, frame_color, frame_style. Required: end, start, summary. 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_event_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_event_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_event_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_event_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_event_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 →