High Risk →

falcon_launch_scheduled_report

Launch a scheduled report on demand

Triggers report generation

Part of the CrowdStrike Falcon MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@falcon-mcp Execute Risk 3/5

AI agents invoke falcon_launch_scheduled_report to trigger processes or run actions in CrowdStrike Falcon. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

falcon_launch_scheduled_report can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

crowdstrike.yaml
tools:
  falcon_launch_scheduled_report:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full CrowdStrike Falcon policy for all 33 tools.

Tool Name falcon_launch_scheduled_report
Category Execute
Risk Level High

View all 33 tools →

Agents calling execute-class tools like falcon_launch_scheduled_report have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

falcon_launch_scheduled_report is one of the high-risk operations in CrowdStrike Falcon. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the falcon_launch_scheduled_report tool do? +

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.

How do I enforce a policy on falcon_launch_scheduled_report? +

Add a rule in your Intercept YAML policy under the tools section for falcon_launch_scheduled_report. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the CrowdStrike Falcon MCP server.

What risk level is falcon_launch_scheduled_report? +

falcon_launch_scheduled_report is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit falcon_launch_scheduled_report? +

Yes. Add a rate_limit block to the falcon_launch_scheduled_report rule in your Intercept 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.

How do I block falcon_launch_scheduled_report completely? +

Set action: deny in the Intercept 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.

What MCP server provides falcon_launch_scheduled_report? +

falcon_launch_scheduled_report is provided by the CrowdStrike Falcon MCP server (@falcon-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on CrowdStrike Falcon

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.