unclick_generate_qr
Generate a QR code from text or a URL. Returns base64-encoded PNG or SVG.
This record as markdown: /tools/creativelead-unclick/unclick-generate-qr.md
What unclick_generate_qr does on UnClick
AI agents invoke unclick_generate_qr to trigger actions in UnClick. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
size | number | — | Image size in pixels (100–1000) |
text | string | — | Text or URL to encode in the QR code |
format | string | — |
Parameters from the server's own tool schema.
Why unclick_generate_qr is rated High
This tool executes a transformation/generation operation — taking input text or URL and producing an encoded image output. It is not a pure read (no data retrieval), not a write to a persistent store, and has no destructive or financial implications. It triggers an external computation to produce an artifact, fitting the Execute category.
From the tool's definition Generate a QR code from text or a URL. Returns base64-encoded PNG or SVG.
Attacks that exploit this kind of access
The rule that runs unclick_generate_qr safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unclick_generate_qr, this is the rule to start with:
unclick_generate_qr stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every unclick_generate_qr call is checked against it from then on.
Questions about unclick_generate_qr
Generate a QR code from text or a URL. Returns base64-encoded PNG or SVG. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
unclick_generate_qr accepts 3 parameters: size, text, format. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for unclick_generate_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 UnClick. Nothing to install.
unclick_generate_qr is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the unclick_generate_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 unclick_generate_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.
unclick_generate_qr is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
Across the catalogue