Lists trend reports showing ranking changes over time. These are AUTO-GENERATED when 2+ scans are run with IDENTICAL settings (same Place ID, keyword, coordinates, grid size, radius, platform). Each trend report tracks one location + one keyword combination. Requires at least 2 matching scans to ...
AI agents call listLocalFalconTrendReports 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 retrieves pre-generated trend reports showing historical ranking changes. It has no side effects, creates no new data, executes no commands, and modifies nothing. It is purely a read operation that queries and presents existing SEO analytics data from the Local Falcon API.
From the tool's definition Tool 'Lists trend reports' — retrieves and queries historical ranking data. Description states it 'Lists' and 'tracks' data without mentioning creation, modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access listLocalFalconTrendReports 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 listLocalFalconTrendReports:
{
"version": "1",
"default": "deny",
"tools": {
"listLocalFalconTrendReports": {}
}
}listLocalFalconTrendReports 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.
Lists trend reports showing ranking changes over time. These are AUTO-GENERATED when 2+ scans are run with IDENTICAL settings (same Place ID, keyword, coordinates, grid size, radius, platform). Each trend report tracks one location + one keyword combination. Requires at least 2 matching scans to exist. NOT generated for campaign scans — that historical data is in the campaign report. Use fieldmask to control returned fields. Recommended fieldmask:. 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 listLocalFalconTrendReports: 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.
listLocalFalconTrendReports 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 listLocalFalconTrendReports 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 listLocalFalconTrendReports. 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.
listLocalFalconTrendReports 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.