Get enriched scan analytics for a QR code. Returns total scans, daily trends, device/browser/country/referer breakdowns with percentages, and recent scan events with parsed user-agent and geo data.
AI agents call get_qr_analytics to retrieve information from QR for Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
period | string | — | Time period for aggregations. Default: 30d. |
short_id | string | Yes | The short ID of the QR code to get analytics for. |
Parameters from the server's own tool schema.
This tool queries and retrieves analytics data about QR code scans. It performs no write, delete, execution, or financial operations. The worst-case misuse would be unauthorized viewing of analytics for QR codes an agent shouldn't access, which is a read authorization issue rather than a capability risk.
From the tool's definition The tool description explicitly states 'Get enriched scan analytics' and 'Returns total scans, daily trends, device/browser/country/referer breakdowns' — all retrieval operations with no modification, deletion, or side effects.
Attacks that exploit this kind of access
Get enriched scan analytics for a QR code. Returns total scans, daily trends, device/browser/country/referer breakdowns with percentages, and recent scan events with parsed user-agent and geo data. It is categorised as a Read tool in the QR for Agent MCP Server, which means it retrieves data without modifying state.
get_qr_analytics accepts 2 parameters: period, short_id. Required: short_id. The full parameter table on this page comes from the server's own tool schema.
Register the QR for Agent MCP server in PolicyLayer and add a rule for get_qr_analytics: 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 for Agent. Nothing to install.
get_qr_analytics 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_qr_analytics 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_qr_analytics. 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_qr_analytics is provided by the QR for Agent MCP server (qr-for-agent). 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 →