get_benchmark
Per-vendor benchmark card by slug within any theme: full provenanced record plus dataset-derived indicators (entry price, normalized cost at 100 and 500 calls/mo where call-volume applies, billing models, free-tier presence, compliance, integration breadth). Set section to the theme slug from lis...
This record as markdown: /tools/com-frontdeskreview-front-desk-review-data/get-benchmark.md
What get_benchmark does on The Front Desk Review
AI agents call get_benchmark 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 |
|---|---|---|---|
slug | string | 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 get_benchmark is rated Low
get_benchmark performs a read-only data retrieval operation. It fetches pre-computed benchmark cards and indicators (entry price, normalized cost, billing models, compliance, integration breadth) indexed by vendor slug and theme. No parameters suggest code execution, data modification, deletion, or financial transactions.
From the tool's definition Tool retrieves and queries benchmark data by vendor slug within a theme, returning "full provenanced record plus dataset-derived indicators" with no mutation, deletion, or execution capability mentioned.
Attacks that exploit this kind of access
The rule that runs get_benchmark 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 get_benchmark, this is the rule to start with:
get_benchmark 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 get_benchmark call is checked against it from then on.
Questions about get_benchmark
Per-vendor benchmark card by slug within any theme: full provenanced record plus dataset-derived indicators (entry price, normalized cost at 100 and 500 calls/mo where call-volume applies, billing models, free-tier presence, compliance, integration breadth). Set section to the theme slug from list_sections. All values trace to plan sources; no synthetic scores. It is categorised as a Read tool in the The Front Desk Review MCP Server, which means it retrieves data without modifying state.
get_benchmark accepts 2 parameters: slug, section. Required: slug. 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 get_benchmark: 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.
get_benchmark 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 get_benchmark 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 get_benchmark. 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.
get_benchmark 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