Detect and decode QR codes.
AI agents call detect_qrcode to retrieve information from farshid-mcp-imageProcessing without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs image analysis to locate and decode QR codes, which is fundamentally a read operation—it retrieves data from visual input. However, severity is elevated to 'medium' rather than 'low' because decoded QR codes often contain URLs, payment links, or commands that could be malicious if an AI agent blindly follows them without validation.
From the tool's definition Tool name: detect_qrcode; description: 'Detect and decode QR codes.' The tool reads and extracts data from QR codes in images without modifying, deleting, or executing code based on the extracted content.
Attacks that exploit this kind of access
Detect and decode QR codes. It is categorised as a Read tool in the farshid-mcp-imageProcessing MCP Server, which means it retrieves data without modifying state.
Register the farshid-mcp-imageProcessing MCP server in PolicyLayer and add a rule for detect_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 farshid-mcp-imageProcessing. Nothing to install.
detect_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 detect_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 detect_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.
detect_qrcode is provided by the farshid-mcp-imageProcessing MCP server (pirahansiah/farshid-mcp-imageprocessing). 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 →