Get conversion statistics for a QR code. Returns total conversions, total value, breakdowns by event name, daily trends, and recent events. Use this to measure QR code ROI and understand which codes drive the most value.
AI agents call get_conversions 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 |
|---|---|---|---|
event | string | — | Filter by event name (e.g., 'purchase'). |
period | string | — | Time period for aggregations. Default: 30d. |
short_id | string | Yes | The short_id of the QR code to get conversion stats for. |
Parameters from the server's own tool schema.
This tool retrieves and reports analytics data (conversions, trends, ROI metrics) without modifying any state or triggering external operations. It is a pure read/query operation with minimal blast radius if misused by an agent—worst case would be accessing statistics it shouldn't see, not causing harm to systems or data integrity.
From the tool's definition Tool name 'get_conversions' and description states it 'returns' and 'get' conversion statistics—queries data about QR code performance metrics with no side effects (no create, update, delete, or execute operations).
Attacks that exploit this kind of access
Get conversion statistics for a QR code. Returns total conversions, total value, breakdowns by event name, daily trends, and recent events. Use this to measure QR code ROI and understand which codes drive the most value. It is categorised as a Read tool in the QR for Agent MCP Server, which means it retrieves data without modifying state.
get_conversions accepts 3 parameters: event, 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_conversions: 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_conversions 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_conversions 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_conversions. 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_conversions 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 →