Lists campaign reports in the account. Campaigns are the primary method for scheduled, recurring scans across multiple locations and/or keywords. Can be configured as: single location + single keyword, multiple locations + single keyword, single location + multiple keywords, or multiple locations...
AI agents call listLocalFalconCampaignReports 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 is a retrieval operation that queries existing campaign report data. It has no side effects, does not execute commands, and does not modify, delete, or create resources. It is a standard Read category tool appropriate for data discovery and analysis in SEO reporting workflows. Low severity due to the informational nature of SEO campaign metadata.
From the tool's definition Tool lists campaign reports and retrieves data without modifying, creating, or deleting resources. Description states 'Lists campaign reports in the account' with control via fieldmask for filtered retrieval. No mutative operations are mentioned.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access listLocalFalconCampaignReports 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 listLocalFalconCampaignReports:
{
"version": "1",
"default": "deny",
"tools": {
"listLocalFalconCampaignReports": {}
}
} listLocalFalconCampaignReports 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 campaign reports in the account. Campaigns are the primary method for scheduled, recurring scans across multiple locations and/or keywords. Can be configured as: single location + single keyword, multiple locations + single keyword, single location + multiple keywords, or multiple locations + multiple keywords. Campaign scans consolidate all data in the campaign report — no separate location/keyword/trend reports are generated. 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 listLocalFalconCampaignReports: 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.
listLocalFalconCampaignReports 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 listLocalFalconCampaignReports 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 listLocalFalconCampaignReports. 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.
listLocalFalconCampaignReports 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.