Lists ONLY individually scheduled automatic scans. NOTE: This does NOT include campaign-scheduled scans, which are the more common way to schedule recurring scans. To see campaign schedules, use listLocalFalconCampaignReports instead. Most users schedule scans through campaigns for better organiz...
AI agents call listLocalFalconAutoScans 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 displays information about scheduled scans without modifying, deleting, or executing any operations. It is a simple query/list operation with no capability to modify state, delete data, or trigger external actions. The blast radius of misuse is minimal - an agent could only view scan schedules, not alter them or cause other damage.
From the tool's definition Tool name 'listLocalFalconAutoScans' and description 'Lists ONLY individually scheduled automatic scans' - the verb 'lists' indicates data retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access listLocalFalconAutoScans 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 listLocalFalconAutoScans:
{
"version": "1",
"default": "deny",
"tools": {
"listLocalFalconAutoScans": {}
}
}listLocalFalconAutoScans 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 ONLY individually scheduled automatic scans. NOTE: This does NOT include campaign-scheduled scans, which are the more common way to schedule recurring scans. To see campaign schedules, use listLocalFalconCampaignReports instead. Most users schedule scans through campaigns for better organization and reporting. 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 listLocalFalconAutoScans: 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.
listLocalFalconAutoScans 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 listLocalFalconAutoScans 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 listLocalFalconAutoScans. 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.
listLocalFalconAutoScans 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.