Create a file/document QR code. Provide the file via file_path (local),
AI agents use create_file_qrcode 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 creates and stores new QR code objects, which constitutes data creation. It is reversible (evidenced by the presence of delete_qrcode on the same server), so it falls under Write rather than Destructive.
From the tool's definition Tool name 'create_file_qrcode' and description 'Create a file/document QR code' indicate the tool creates new QR code records in the QR Forge system. The action is reversible (QR codes can be deleted via sibling tool 'delete_qrcode').
Attacks that exploit this kind of access
Create a file/document QR code. Provide the file via file_path (local),. 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 create_file_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.
create_file_qrcode 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 create_file_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 create_file_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.
create_file_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 →