list_coverage
What this index actually covers, so a miss reads as out-of-scope rather than broken. Now spans 271 pricing themes — the deep hub sections PLUS dozens of catalog topics (VPNs, web hosting, password managers, CRM, e-commerce, AI tools, and more): total theme count, the section/catalog split, total ...
This record as markdown: /tools/com-frontdeskreview-front-desk-review-data/list-coverage.md
What list_coverage does on The Front Desk Review
AI agents call list_coverage 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.
Why list_coverage is rated Low
This tool retrieves and reports on the scope and contents of the product/pricing database index. It is purely informational, answering questions about what data exists and its coverage without creating, modifying, executing code, deleting, or committing financial transactions. The lowest risk category (Read) applies.
From the tool's definition Tool name 'list_coverage' and description indicates it provides informational metadata about what the index covers — 'total theme count', 'section/catalog split', 'total vendors', 'per-theme vendor counts', 'data's date range', 'questions it answers well and…
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs list_coverage 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 list_coverage, this is the rule to start with:
list_coverage 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 list_coverage call is checked against it from then on.
Questions about list_coverage
What this index actually covers, so a miss reads as out-of-scope rather than broken. Now spans 271 pricing themes — the deep hub sections PLUS dozens of catalog topics (VPNs, web hosting, password managers, CRM, e-commerce, AI tools, and more): total theme count, the section/catalog split, total vendors, per-theme vendor counts and kind, the data's date range (min/max source accessedAt), the questions it answers well and what it does NOT cover. Derived from every theme's dataset. It is categorised as a Read tool in the The Front Desk Review MCP Server, which means it retrieves data without modifying state.
Register the The Front Desk Review MCP server in PolicyLayer and add a rule for list_coverage: 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.
list_coverage 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 list_coverage 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 list_coverage. 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.
list_coverage 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