whats_changed
Recent dated price-change capsules, newest first — the freshness a base model cannot have. Each capsule is a cleared, two-source-corroborated movement of a vendor's published price (vendor, plan, before→after, date, sources). Optionally filter to changes on/after a date or within one section. Ret...
This record as markdown: /tools/com-frontdeskreview-front-desk-review-data/whats-changed.md
What whats_changed does on The Front Desk Review
AI agents call whats_changed 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 |
|---|---|---|---|
since | string | — | Only changes detected on or after this ISO date (YYYY-MM-DD). |
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 whats_changed is rated Low
Retrieves historical price change data with no side effects.
From the tool's definition Recent dated price-change capsules, newest first
Attacks that exploit this kind of access
The rule that runs whats_changed 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 whats_changed, this is the rule to start with:
whats_changed 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 whats_changed call is checked against it from then on.
Questions about whats_changed
Recent dated price-change capsules, newest first — the freshness a base model cannot have. Each capsule is a cleared, two-source-corroborated movement of a vendor's published price (vendor, plan, before→after, date, sources). Optionally filter to changes on/after a date or within one section. Returns an empty list with a clear note when nothing qualifying has been recorded yet. It is categorised as a Read tool in the The Front Desk Review MCP Server, which means it retrieves data without modifying state.
whats_changed accepts 2 parameters: since, section. 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 whats_changed: 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.
whats_changed 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 whats_changed 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 whats_changed. 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.
whats_changed 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