List all managed QR codes with pagination. Returns short IDs, target URLs, labels, and timestamps. Use this to browse or search for existing QR codes.
AI agents call list_qr_codes to retrieve information from QR for Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Max results to return. |
offset | number | — | Number of results to skip. |
Parameters from the server's own tool schema.
This tool purely retrieves and queries stored QR code metadata with no side effects. It matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The severity is low because exposure of QR code metadata poses minimal risk—these are typically non-sensitive identifiers and URLs. Confidence is high based on clear read-only semantics in the name and description.
From the tool's definition list_qr_codes returns metadata about QR codes (short IDs, target URLs, labels, timestamps) with pagination. No creation, modification, or deletion occurs. The description explicitly states 'browse or search for existing QR codes.'
Attacks that exploit this kind of access
List all managed QR codes with pagination. Returns short IDs, target URLs, labels, and timestamps. Use this to browse or search for existing QR codes. It is categorised as a Read tool in the QR for Agent MCP Server, which means it retrieves data without modifying state.
list_qr_codes accepts 2 parameters: limit, offset. 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 list_qr_codes: 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.
list_qr_codes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_qr_codes 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 list_qr_codes. 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.
list_qr_codes 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.
list_qr_codes is one line of QR for Agent's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →