Retrieves a specific trend report showing historical ARP, ATRP, and SoLV changes across multiple scan dates for one location + one keyword. Returns: scans array (historical snapshots with date, ARP, ATRP, SoLV, grid images per scan), locations array (competitor leaderboard with aggregated metrics...
AI agents call getLocalFalconTrendReport to retrieve information from Local Falcon MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches and returns historical reporting data (ARP, ATRP, SoLV metrics, competitor leaderboards, GBP profiles) for SEO analysis. It has no side effects—it does not create, modify, delete, or execute actions. The data returned is read-only snapshots used for trend analysis.
From the tool's definition Tool name 'getLocalFalconTrendReport' and description 'Retrieves a specific trend report' and 'Returns: scans array (historical snapshots...)' indicate a retrieval-only operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access getLocalFalconTrendReport gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Local Falcon MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for getLocalFalconTrendReport:
{
"version": "1",
"default": "deny",
"tools": {
"getLocalFalconTrendReport": {}
}
} getLocalFalconTrendReport is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieves a specific trend report showing historical ARP, ATRP, and SoLV changes across multiple scan dates for one location + one keyword. Returns: scans array (historical snapshots with date, ARP, ATRP, SoLV, grid images per scan), locations array (competitor leaderboard with aggregated metrics across all scans), location object (full GBP profile of the target business), and top-level metadata (keyword, grid config, PDF link). Heavy nested data (data_points, per-scan locations) is automatically stripped to save context. STRONGLY RECOMMEND fieldmask — trend reports with many historical scans can grow large (scans[] array scales with snapshot count). Recommended fieldmask (Maps-platform trend reports):. It is categorised as a Read tool in the Local Falcon MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Local Falcon MCP Server MCP server in PolicyLayer and add a rule for getLocalFalconTrendReport: 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 Local Falcon MCP Server. Nothing to install.
getLocalFalconTrendReport 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 getLocalFalconTrendReport 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 getLocalFalconTrendReport. 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.
getLocalFalconTrendReport is provided by the Local Falcon MCP Server MCP server (local-falcon/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Local Falcon MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
37 Local Falcon MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.