Download a file-backed QR code's current file. With save_path, writes it
AI agents call download_qrcode_file 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.
The tool retrieves and downloads an existing QR code file, which is a read operation with no side effects or data modification. Even though it writes to a local save_path, this is a client-side artifact and does not modify the server state or underlying data. The blast radius of misuse is minimal—an agent could only access files already associated with QR codes it has authorization to download.
From the tool's definition Tool description explicitly states 'Download a file-backed QR code's current file.' Download and read operations retrieve data without modifying or deleting the underlying QR code or file.
Attacks that exploit this kind of access
Download a file-backed QR code's current file. With save_path, writes it. 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 download_qrcode_file: 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.
download_qrcode_file 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 download_qrcode_file 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 download_qrcode_file. 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.
download_qrcode_file 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 →