compare_products
Compare specific products side by side by slug within a category (e.g. ['apple-iphone-16-pro','samsung-galaxy-s25-ultra'] in 'smartphones'). Returns full provenanced spec records plus a notFound list and the category's comparable specKeys, so an agent can line up the same attributes across products.
This record as markdown: /tools/com-frontdeskreview-front-desk-review-data/compare-products.md
What compare_products does on The Front Desk Review
AI agents call compare_products to retrieve information from The Front Desk Review 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 |
|---|---|---|---|
slugs | array | Yes | |
category | string | Yes | Product category slug from list_product_categories. |
Parameters from the server's own tool schema.
Why compare_products is rated Low
This tool queries an existing product database and returns comparative information without any side effects. It performs a read-only operation that retrieves structured product specification data for comparison purposes. The low severity reflects that misuse would only expose product information without enabling financial, destructive, or system-level harm.
From the tool's definition The tool 'compare_products' retrieves and returns 'full provenanced spec records' and 'comparable specKeys' for products.
Attacks that exploit this kind of access
The rule that runs compare_products safely
PolicyLayer is an MCP gateway: it sits between your AI agents and The Front Desk Review, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For compare_products, this is the rule to start with:
compare_products 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 The Front Desk Review, apply this rule, and every compare_products call is checked against it from then on.
Questions about compare_products
Compare specific products side by side by slug within a category (e.g. ['apple-iphone-16-pro','samsung-galaxy-s25-ultra'] in 'smartphones'). Returns full provenanced spec records plus a notFound list and the category's comparable specKeys, so an agent can line up the same attributes across products. It is categorised as a Read tool in the The Front Desk Review MCP Server, which means it retrieves data without modifying state.
compare_products accepts 2 parameters: slugs, category. Required: slugs, category. The full parameter table on this page comes from the server's own tool schema.
Register the The Front Desk Review MCP server in PolicyLayer and add a rule for compare_products: 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 The Front Desk Review. Nothing to install.
compare_products 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 compare_products 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 compare_products. 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.
compare_products is provided by the The Front Desk Review MCP server (https://mcp.frontdeskreview.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on The Front Desk Review, and thousands of servers like it.
This server
Across the catalogue