Replace a file-backed QR code's file while keeping its QR/link unchanged.
AI agents use replace_qrcode_file to create or update resources in QR Forge MCP server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QR Forge MCP server environment.
This tool modifies existing data (the file associated with a QR code) in a reversible manner. It updates the file content while preserving the QR code structure itself, making it a Write operation rather than Destructive.
From the tool's definition The tool performs a replace operation on a file-backed QR code's underlying file content while maintaining the QR code and link identity. The description explicitly states 'Replace a file-backed QR code's file', which modifies data reversibly.
Attacks that exploit this kind of access
Replace a file-backed QR code's file while keeping its QR/link unchanged. It is categorised as a Write tool in the QR Forge MCP server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the QR Forge MCP server MCP server in PolicyLayer and add a rule for replace_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.
replace_qrcode_file 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 replace_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 replace_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.
replace_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 →