Skip to content

Aembit supports the open source CrowdStrike Falcon MCP server, which lets AI Agent: A software workload that authenticates to systems, requests credentials, and accesses resources, either on behalf of a person or on its own. Aembit secures AI agents with the same identity-first model it uses for any workload. User-driven agents such as Claude Desktop also carry a blended identity that ties access to both the user and the agent.Learn more query CrowdStrike Falcon detections, hosts, intelligence, and other security data through Model Context Protocol: A standard protocol for AI agent and server interactions that defines how AI assistants communicate with external tools and data sources.Learn more(opens in new tab) tools.

You run the Falcon MCP server yourself as an MCP Server: A server that implements the Model Context Protocol to provide tools, resources, or data to AI agents and MCP clients.Learn more(opens in new tab). The Aembit MCP Identity Gateway: A component that brokers MCP traffic between MCP clients and target MCP servers, validating authorization and presenting Aembit-managed credentials on each request.Learn more authenticates to it with a static API key that all users share.

This guide builds the Gateway-to-Server Policy: The Access Policy that authorizes the MCP Identity Gateway to access an MCP server on behalf of authenticated users—the Gateway itself is the Client Workload. Also called right-side auth; each MCP server behind the Gateway needs its own.Learn more—the second of the two Access Policy: Access Policies define, enforce, and audit access between Client and Server Workloads by cryptographically verifying workload identity and contextual factors rather than relying on static secrets.Learn more the MCP Identity Gateway requires. You create the first, the Client-to-Gateway Policy: The Access Policy that validates which MCP client can connect to the MCP Identity Gateway and authenticates users through your Identity Provider. Also called left-side auth; you create one per MCP client and Gateway combination.Learn more, during Gateway setup.

Before you begin, ensure you have the following:

  • A paid CrowdStrike Falcon subscription with API access, and permission to create API clients in the Falcon console
  • A host where you can run falcon-mcp behind a TLS reverse proxy that MCP Identity Gateway can reach
  • A configured Aembit MCP Identity Gateway

Before you configure CrowdStrike Falcon, review these requirements and behaviors specific to the Falcon MCP server.

  • Use an API Key Credential Provider. The Falcon MCP server accepts one static API key and has no OAuth or per-user authentication. Every user who reaches it through MCP Identity Gateway shares that key and the Falcon API client’s permissions.
  • You host the server. You run CrowdStrike’s falcon-mcp server in your own infrastructure, and Aembit-managed MCP Identity Gateway deployments connect only to MCP servers at publicly reachable addresses.
  • Aembit provides only the server’s API key. The server keeps the Falcon API client ID and secret in its own configuration and uses them to call the Falcon API.
  • The default tool set exceeds the Copilot Studio tool limit. With no module selection, falcon-mcp enables every module and registers more than 100 tools, while Copilot Studio drops tools past about 70.
  • The default tool set can change your Falcon environment. Many modules carry tools that create, update, or delete Falcon resources, and FALCON_MCP_READ_ONLY=true registers only read-only tools.
  • The server is pre-1.0. CrowdStrike can change tool names, parameters, and responses between minor releases, so pin a version.

CrowdStrike does not host an MCP endpoint, so you run falcon-mcp yourself and put a TLS endpoint in front of it. CrowdStrike’s falcon-mcp repository covers installation and every configuration option.

  1. In the Falcon console, go to Support and resources > API clients and keys and create an API client with the scopes for the modules you plan to enable. Note the client ID, the client secret, and your Falcon region’s API base URL.

  2. Generate a random API key for the MCP server, for example with openssl rand -hex 32. The Aembit Credential Provider stores this key later.

  3. Configure falcon-mcp with the following environment variables:

    VariableValue
    FALCON_CLIENT_IDThe API client ID
    FALCON_CLIENT_SECRETThe API client secret
    FALCON_BASE_URLYour Falcon region’s API base URL
    FALCON_MCP_TRANSPORTstreamable-http
    FALCON_MCP_API_KEYThe API key you generated
    FALCON_MCP_READ_ONLYtrue, unless AI agents need to change Falcon data
  4. Start falcon-mcp. It serves the MCP endpoint at /mcp over plain HTTP, on 127.0.0.1:8000 by default.

  5. Put a TLS reverse proxy in front of the server, such as nginx with a certificate from a public certificate authority. Keep the plain HTTP port off the network, because MCP Identity Gateway sends the API key in every request. Note the reverse proxy’s host and port, such as https://<falcon-mcp-host>:9000/mcp.

Create an API Key Credential Provider: Credential Providers obtain the specific access credentials—such as API keys, OAuth tokens, or temporary cloud credentials—that Client Workloads need to authenticate to Server Workloads.Learn more in Aembit.

  1. Log into your Aembit Tenant: Aembit Tenants serve as isolated, dedicated environments within Aembit that provide complete separation of administrative domains and security configurations.Learn more.

  2. Go to Credential Providers in the left sidebar and click + New.

  3. Configure the following fields:

    FieldValue
    NameA user-friendly name
    Credential TypeAPI Key
    API KeyThe value you set for FALCON_MCP_API_KEY on the server
  4. Click Save.

  1. Go to Server Workloads in the left sidebar and click + New.

  2. Configure the following fields:

    FieldValue
    NameA user-friendly name
    HostThe domain name of your TLS reverse proxy
    Application ProtocolMCP
    PortThe reverse proxy’s port, with TLS selected
    URL Path/mcp
    Authentication MethodAPI Key
    Authentication SchemeHeader
    Headerx-api-key
  3. Click Save.

On the Select Existing tab, select the API Key Credential Provider you created and click Use Selected. The linked setup procedure describes creating a new Credential Provider.

This section creates the Gateway-to-Server Access Policy, which authorizes MCP Identity Gateway to access CrowdStrike Falcon.

Create an Access Policy linking MCP Identity Gateway (as the Client Workload: Client Workloads represent AI agents, software applications, scripts, or automated processes that initiate access requests to Server Workloads. They can act on behalf of a user under blended identity or operate autonomously, as when one service calls another.Learn more), the Credential Provider you created, and the Server Workload for CrowdStrike Falcon.

For step-by-step instructions, including the Client Workload settings that identify MCP Identity Gateway, see Create the gateway-to-server Access Policy.

After you create the Access Policy, connect an AI agent through MCP Identity Gateway and list its tools. The list includes the falcon_-prefixed tools that your falcon-mcp configuration enables.