generate_qr_code
Generate a bounded PNG or SVG QR code locally from caller-supplied text or a URL. Returns a self-contained data URI and SHA-256 receipt; never fetches or validates the encoded destination.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/generate-qr-code.md
What generate_qr_code does on Delx Mcp A2a
AI agents use generate_qr_code to create or update resources in Delx Mcp A2a, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Delx Mcp A2a environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
data | string | Yes | Text or URL to encode; it is not fetched or validated. |
text | string | — | Alias for data. |
border | integer | — | |
format | string | — | |
box_size | integer | — | |
error_correction | string | — |
Parameters from the server's own tool schema.
Why generate_qr_code is rated Medium
This tool creates a new QR code image from caller-supplied input and returns it as a data URI, which is a write operation that produces a reversible artifact. It does not execute code, delete data, move funds, or trigger external operations.
From the tool's definition Tool generates and returns a QR code (PNG or SVG) as a new artifact; returns 'a self-contained data URI and SHA-256 receipt', indicating creation of output content.
Attacks that exploit this kind of access
The rule that runs generate_qr_code safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Mcp A2a, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For generate_qr_code, this is the rule to start with:
generate_qr_code 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 Delx Mcp A2a, apply this rule, and every generate_qr_code call is checked against it from then on.
Questions about generate_qr_code
Generate a bounded PNG or SVG QR code locally from caller-supplied text or a URL. Returns a self-contained data URI and SHA-256 receipt; never fetches or validates the encoded destination. It is categorised as a Write tool in the Delx Mcp A2a MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
generate_qr_code accepts 6 parameters: data, text, border, format, box_size, error_correction. Required: data. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for generate_qr_code: 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 Delx Mcp A2a. Nothing to install.
generate_qr_code 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 generate_qr_code 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 generate_qr_code. 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.
generate_qr_code is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
This server
Across the catalogue