compare
Compare specific vendors side by side by slug within any theme (e.g. ['goodcall','rosie','smith-ai'] in ai-receptionists, or ['nordvpn','expressvpn'] in vpn-services). Set section to the theme slug from list_sections. Returns full provenanced records plus a notFound list for unknown slugs.
This record as markdown: /tools/com-frontdeskreview-front-desk-review-data/compare.md
What compare does on The Front Desk Review
AI agents call compare 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 | |
section | string | — | Theme slug to query (default "ai-receptionists"). A theme is any of the 271 pricing topics this index covers: the deep hub sections (e.g. ai-receptionists) plus |
Parameters from the server's own tool schema.
Why compare is rated Low
Tool only retrieves and returns vendor comparison data with no side effects.
From the tool's definition Compare specific vendors side by side... Returns full provenanced records
Attacks that exploit this kind of access
The rule that runs compare 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, this is the rule to start with:
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 The Front Desk Review, apply this rule, and every compare call is checked against it from then on.
Questions about compare
Compare specific vendors side by side by slug within any theme (e.g. ['goodcall','rosie','smith-ai'] in ai-receptionists, or ['nordvpn','expressvpn'] in vpn-services). Set section to the theme slug from list_sections. Returns full provenanced records plus a notFound list for unknown slugs. It is categorised as a Read tool in the The Front Desk Review MCP Server, which means it retrieves data without modifying state.
compare accepts 2 parameters: slugs, section. Required: slugs. 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: 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 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 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. 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 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