File-replacement history for a file-backed QR code (newest first).
AI agents call get_qrcode_history 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 and queries historical data about QR code file replacements. It performs no side effects, creates no new data, executes no commands, and does not delete or modify anything. It is purely informational access to past states of a file-backed QR code, making it a straightforward Read category tool with low severity since accessing history poses minimal security risk.
From the tool's definition Tool name 'get_qrcode_history' and description 'File-replacement history for a file-backed QR code (newest first)' indicate retrieval of historical information.
Attacks that exploit this kind of access
File-replacement history for a file-backed QR code (newest first). 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_history: 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_history 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_history 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_history. 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_history 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 →