Get a single QR code's details by id. Use get_qrcode_png to view the image.
AI agents call get_qrcode to retrieve information from QR Forge MCP server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing QR code metadata without creating, modifying, or deleting any data. It has no capacity to alter state or trigger external actions. The blast radius of misuse is minimal—an attacker could only enumerate or view QR codes they may or may not have authorization to access, which is a confidentiality concern but not integrity or availability. Severity is low.
From the tool's definition Tool name and description indicate retrieval only: 'Get a single QR code's details by id'. The phrase 'Use get_qrcode_png to view the image' further confirms this is a query/fetch operation with no side effects.
Attacks that exploit this kind of access
Get a single QR code's details by id. Use get_qrcode_png to view the image. It is categorised as a Read tool in the QR Forge MCP server MCP Server, which means it retrieves data without modifying state.
Register the QR Forge MCP server MCP server in PolicyLayer and add a rule for get_qrcode: 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 Forge MCP server. Nothing to install.
get_qrcode 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 get_qrcode 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 get_qrcode. 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.
get_qrcode is provided by the QR Forge MCP server MCP server (jkolarov/qrforge-mcp). 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 →