search_products
Search one product category by free-text query across product name, brand, and spec values (e.g. 'snapdragon 5000mah', 'oled 120hz'). Set category to a slug from list_product_categories. Returns full provenanced product records (every spec + price carries source url + accessedAt). Empty query ret...
This record as markdown: /tools/com-frontdeskreview-front-desk-review-data/search-products.md
What search_products does on The Front Desk Review
AI agents call search_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 |
|---|---|---|---|
query | string | — | |
category | string | Yes | Product category slug from list_product_categories (e.g. 'smartphones'). |
Parameters from the server's own tool schema.
Why search_products is rated Low
This tool retrieves and queries product data by free-text search within a category. It has no write, execute, or destructive capabilities—it only reads and returns existing product information. The blast radius of misuse is minimal; an agent could retrieve large datasets but cannot modify, delete, or trigger external actions.
From the tool's definition Tool description states it 'Search[es]' and 'Returns full provenanced product records' without any mutation or deletion capability. The verb is strictly retrieval-based ('search', 'returns'). No side effects, modifications, or data destruction are mentioned.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs search_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 search_products, this is the rule to start with:
search_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 search_products call is checked against it from then on.
Questions about search_products
Search one product category by free-text query across product name, brand, and spec values (e.g. 'snapdragon 5000mah', 'oled 120hz'). Set category to a slug from list_product_categories. Returns full provenanced product records (every spec + price carries source url + accessedAt). Empty query returns all products in the category. It is categorised as a Read tool in the The Front Desk Review MCP Server, which means it retrieves data without modifying state.
search_products accepts 2 parameters: query, category. Required: 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 search_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.
search_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 search_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 search_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.
search_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