qrserver_generate
Generate a QR code image URL for any text or URL.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/qrserver-generate.md
What qrserver_generate does on UnClick
AI agents use qrserver_generate to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Text or URL to encode in the QR code. |
size | string | — | Image dimensions as WxH (default '200x200'). |
color | string | — | QR code color as hex without # (e.g. '000000'). |
format | string | — | Image format: png, svg, jpg (default 'png'). |
bgcolor | string | — | Background color as hex without # (e.g. 'ffffff'). |
Parameters from the server's own tool schema.
Why qrserver_generate is rated Medium
Generating a QR code is a data creation action (Write category) rather than retrieval (Read). It produces a new resource/output. However, severity is low because QR code generation has minimal blast radius—it cannot modify existing data, delete anything, execute code, or move money. The generated QR code is benign and contains only the text or URL provided as input.
From the tool's definition Tool generates and creates a QR code image URL as output. The description states 'Generate a QR code image URL' which indicates creation of new data/resource.
Attacks that exploit this kind of access
The rule that runs qrserver_generate 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 qrserver_generate, this is the rule to start with:
qrserver_generate stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 qrserver_generate call is checked against it from then on.
Questions about qrserver_generate
Generate a QR code image URL for any text or URL. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
qrserver_generate accepts 5 parameters: data, size, color, format, bgcolor. Required: data. 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 qrserver_generate: 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.
qrserver_generate 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 qrserver_generate 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 qrserver_generate. 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.
qrserver_generate is provided by the UnClick MCP server (@unclick/mcp-server). 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.
This server
Across the catalogue