List all supported QR data types (WiFi, vCard, Email, etc.) with their required and optional fields.
AI agents call list_qr_types to retrieve information from QRMint MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and displays metadata about supported QR code types and their field requirements. It performs no creation, modification, deletion, or code execution. It is a pure informational query with no capacity to cause side effects or risk to systems or data.
From the tool's definition Tool name contains 'list' and description states it 'List all supported QR data types' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all supported QR data types (WiFi, vCard, Email, etc.) with their required and optional fields. It is categorised as a Read tool in the QRMint MCP Server MCP Server, which means it retrieves data without modifying state.
Register the QRMint MCP Server MCP server in PolicyLayer and add a rule for list_qr_types: 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 QRMint MCP Server. Nothing to install.
list_qr_types 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 list_qr_types 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 list_qr_types. 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.
list_qr_types is provided by the QRMint MCP Server MCP server (softvoyagers/qrmint-api-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 →