unit_price_compare
Unit Price Comparator — Compare 2+ products' price-per-unit across mass/volume/count, converting units within the same dimension, and flag the best value.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/unit-price-compare.md
What unit_price_compare does on Gateway
AI agents call unit_price_compare to retrieve information from Gateway 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 |
|---|---|---|---|
items | array | Yes | Array of 2+ {name, price, quantity, unit} objects |
Parameters from the server's own tool schema.
Why unit_price_compare is rated Low
This is a pure comparison and calculation tool that reads/retrieves product price information and performs mathematical analysis to determine best value. It has no write, destructive, execute, or financial side effects—it simply processes input data and returns a comparative result.
From the tool's definition Tool description: 'Compare 2+ products' price-per-unit across mass/volume/count, converting units within the same dimension, and flag the best value.' The tool retrieves and compares pricing data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
The rule that runs unit_price_compare safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unit_price_compare, this is the rule to start with:
unit_price_compare 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 Gateway, apply this rule, and every unit_price_compare call is checked against it from then on.
Questions about unit_price_compare
Unit Price Comparator — Compare 2+ products' price-per-unit across mass/volume/count, converting units within the same dimension, and flag the best value. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
unit_price_compare accepts 1 parameter: items. Required: items. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for unit_price_compare: 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 Gateway. Nothing to install.
unit_price_compare 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 unit_price_compare 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 unit_price_compare. 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.
unit_price_compare is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue