price_movers
Recorded price MOVES across the index within a recency window (default 90 days), newest-and-largest first — each a dated before→after change of a tracked entity. Optionally filter by kind ('hw'/'sw') or category/theme slug. The freshness a base model structurally cannot have. Returns an empty lis...
This record as markdown: /tools/com-frontdeskreview-front-desk-review-data/price-movers.md
What price_movers does on The Front Desk Review
AI agents call price_movers 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 |
|---|---|---|---|
kind | string | — | Limit to 'hw' (hardware product) or 'sw' (software vendor). Omit to match either; a slug is resolved across both. |
limit | integer | — | Max movers to return (default 25). |
category | string | — | Limit to one category/theme slug (e.g. '3d-printers', 'ai-receptionists'). |
withinDays | integer | — | Recency window in days (default 90), measured against the log's latest date. |
Parameters from the server's own tool schema.
Why price_movers is rated Low
Tool retrieves historical price movement data with no side effects.
From the tool's definition Recorded price MOVES... returns dated before→after change
Attacks that exploit this kind of access
The rule that runs price_movers 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 price_movers, this is the rule to start with:
price_movers 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 price_movers call is checked against it from then on.
Questions about price_movers
Recorded price MOVES across the index within a recency window (default 90 days), newest-and-largest first — each a dated before→after change of a tracked entity. Optionally filter by kind ('hw'/'sw') or category/theme slug. The freshness a base model structurally cannot have. Returns an empty list with a clear note when nothing moved in the window (a quiet window is honestly quiet). It is categorised as a Read tool in the The Front Desk Review MCP Server, which means it retrieves data without modifying state.
price_movers accepts 4 parameters: kind, limit, category, withinDays. 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 price_movers: 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.
price_movers 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 price_movers 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 price_movers. 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.
price_movers 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