falcon_launch_scheduled_report
Launch a scheduled report on demand
This record as markdown: /tools/crowdstrike/falcon-launch-scheduled-report.md
What falcon_launch_scheduled_report does on CrowdStrike Falcon
AI agents invoke falcon_launch_scheduled_report to trigger actions in CrowdStrike Falcon. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why falcon_launch_scheduled_report is rated High
This tool triggers execution of a scheduled report, which is an external operation with side effects that depend on the arguments provided (which report to launch). This fits the Execute category: 'runs code, shell commands, browser actions, or triggers external operations whose effects depend on arguments.' Severity is medium because while report generation is an operational action, it is not destructive,…
From the tool's definition Tool name 'falcon_launch_scheduled_report' and description 'Launch a scheduled report on demand' indicate triggering an external operation (report generation/execution) whose effects depend on which report is launched.
Risk signalsTriggers report generation
Attacks that exploit this kind of access
The rule that runs falcon_launch_scheduled_report safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CrowdStrike Falcon, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For falcon_launch_scheduled_report, this is the rule to start with:
falcon_launch_scheduled_report stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect CrowdStrike Falcon, apply this rule, and every falcon_launch_scheduled_report call is checked against it from then on.
Questions about falcon_launch_scheduled_report
Launch a scheduled report on demand. It is categorised as a Execute tool in the CrowdStrike Falcon MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the CrowdStrike Falcon MCP server in PolicyLayer and add a rule for falcon_launch_scheduled_report: 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 CrowdStrike Falcon. Nothing to install.
falcon_launch_scheduled_report is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the falcon_launch_scheduled_report 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 falcon_launch_scheduled_report. 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.
falcon_launch_scheduled_report is provided by the CrowdStrike Falcon MCP server (@falcon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CrowdStrike Falcon, and thousands of servers like it.
Across the catalogue