Generate a QR code image for a POI that customers can scan. Endpoint: GET /poi/{poiId}/image Authentication: Public endpoint (no auth required) Use Case: Generate QR codes for printing or displaying on screens. Formats: PNG (default), SVG, JPG Returns base64-encoded image data that can be saved o...
AI agents call payware_poi_get_qrcode to retrieve information from Payware MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation because it retrieves and returns data without modifying any state or triggering consequential side effects. Generating a QR code for display purposes is a retrieval action. The public endpoint with no authentication requirement and the straightforward nature of returning image data further confirm this is low-risk information retrieval.
From the tool's definition The tool 'payware_poi_get_qrcode' generates and returns a QR code image in various formats (PNG, SVG, JPG) as base64-encoded data.
Attacks that exploit this kind of access
Generate a QR code image for a POI that customers can scan. Endpoint: GET /poi/{poiId}/image Authentication: Public endpoint (no auth required) Use Case: Generate QR codes for printing or displaying on screens. Formats: PNG (default), SVG, JPG Returns base64-encoded image data that can be saved or displayed. Required: POI ID only. It is categorised as a Read tool in the Payware MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Payware MCP Server MCP server in PolicyLayer and add a rule for payware_poi_get_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 Payware MCP Server. Nothing to install.
payware_poi_get_qrcode 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 payware_poi_get_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 payware_poi_get_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.
payware_poi_get_qrcode is provided by the Payware MCP Server MCP server (payware/mcp-server). 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 →