Lists existing scan reports. ALWAYS check here before running new scans to avoid duplicates and save credits. Returns report metadata including date, keyword, location, ARP, ATRP, SoLV, grid size, and platform. Use filters to narrow results. If a report has a campaign_key, its data is consolidate...
AI agents call listLocalFalconScanReports 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 and queries existing scan report metadata from the Local Falcon API. It performs a read-only operation that returns historical report data with optional filtering. There is no data creation, modification, deletion, or execution of external operations. The advice to 'check here before running new scans to avoid duplicates' further confirms this is a query/list operation.
From the tool's definition Tool name 'listLocalFalconScanReports' and description 'Lists existing scan reports' with capability to 'Returns report metadata' and 'Use filters to narrow results' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access listLocalFalconScanReports 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 listLocalFalconScanReports:
{
"version": "1",
"default": "deny",
"tools": {
"listLocalFalconScanReports": {}
}
}listLocalFalconScanReports 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 existing scan reports. ALWAYS check here before running new scans to avoid duplicates and save credits. Returns report metadata including date, keyword, location, ARP, ATRP, SoLV, grid size, and platform. Use filters to narrow results. If a report has a campaign_key, its data is consolidated in the campaign report — no separate trend/location/keyword reports exist for campaign scans. Use fieldmask to control returned fields. Recommended fieldmask for browsing: \. 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 listLocalFalconScanReports: 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.
listLocalFalconScanReports 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 listLocalFalconScanReports 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 listLocalFalconScanReports. 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.
listLocalFalconScanReports 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.