Critical Risk →

falcon_remove_iocs

Remove IOCs by IDs or FQL filter

Deletes threat indicators

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

@falcon-mcp Destructive

AI agents may call falcon_remove_iocs to permanently remove or destroy resources in CrowdStrike Falcon. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call falcon_remove_iocs in a loop, permanently destroying resources in CrowdStrike Falcon. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

crowdstrike.yaml
tools:
  falcon_remove_iocs:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full CrowdStrike Falcon policy for all 33 tools.

Tool Name falcon_remove_iocs
Category Destructive
Risk Level Critical

View all 33 tools →

Agents calling destructive-class tools like falcon_remove_iocs 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 Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

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

What does the falcon_remove_iocs tool do? +

Remove IOCs by IDs or FQL filter. It is categorised as a Destructive tool in the CrowdStrike Falcon MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on falcon_remove_iocs? +

Add a rule in your Intercept YAML policy under the tools section for falcon_remove_iocs. 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_remove_iocs? +

falcon_remove_iocs is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit falcon_remove_iocs? +

Yes. Add a rate_limit block to the falcon_remove_iocs 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_remove_iocs completely? +

Set action: deny in the Intercept policy for falcon_remove_iocs. 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_remove_iocs? +

falcon_remove_iocs 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.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

Currently onboarding teams running MCP in production.
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.

// REQUEST EARLY ACCESS

We're letting people in as fast as we can.

You're in the queue.

We'll be in touch as soon as we can let you in.