This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/upc-lookup.md
What upc_lookup does on UnClick
AI agents call upc_lookup to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
upc | string | Yes | UPC or EAN barcode number. |
Parameters from the server's own tool schema.
Why upc_lookup is rated Low
This tool retrieves product information based on a barcode identifier. It performs a query operation that returns data without creating, modifying, deleting, or executing any external operations. The lookup is informational only, making it a Read category tool with low severity.
From the tool's definition Tool is named 'upc_lookup' and described as 'Look up a product by UPC/EAN barcode number.' The verb 'look up' and the read-only nature of querying a barcode database indicate data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs upc_lookup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For upc_lookup, this is the rule to start with:
upc_lookup is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every upc_lookup call is checked against it from then on.
Questions about upc_lookup
Look up a product by UPC/EAN barcode number. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
upc_lookup accepts 1 parameter: upc. Required: upc. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for upc_lookup: 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 UnClick. Nothing to install.
upc_lookup 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 upc_lookup 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 upc_lookup. 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.
upc_lookup is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue