Scan analytics for a dynamic QR code: daily series + totals (days 1-365).
AI agents call get_qrcode_scans 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.
get_qrcode_scans queries and retrieves historical scan data without side effects. It does not create, modify, delete, or execute operations. This is a straightforward data retrieval operation that falls squarely in the Read category. Severity is low because misuse would only expose analytics information about QR code usage, which is typically non-sensitive metadata.
From the tool's definition Tool retrieves scan analytics data (daily series + totals) for a dynamic QR code. Description uses 'analytics' and data retrieval language with no modification, deletion, or execution capabilities mentioned.
Attacks that exploit this kind of access
Scan analytics for a dynamic QR code: daily series + totals (days 1-365). 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_scans: 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_scans 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_scans 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_scans. 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_scans 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 →