# Content Security

> Overview of Content Security Providers and how they govern MCP tool traffic in an Access Policy.

Content Security Providers govern the Model Context Protocol (MCP) tool traffic that flows through Aembit’s MCP Identity Gateway to your MCP servers. You add a provider to an Access Policy through its Content Security component. Each provider evaluates the MCP tool messages the MCP Identity Gateway proxies, and Aembit applies the provider’s decision before the message continues.

## Content Security in an Access Policy

In the Access Policy Builder, Content Security is an optional component positioned between Access Conditions and Credential Providers. See [Create an Access Policy](/user-guide/access-policies/create-access-policy/) for every component an Access Policy can include.

An Access Policy evaluates each Content Security Provider it carries on both the request and response paths of the MCP tool traffic it governs. Evaluation adds a step without changing how the Access Policy’s other components authorize access.

> **Reuse this in another Resource Set**
>
> You can copy a Content Security Provider to another Resource Set. See [About component copying](/user-guide/administration/resource-sets/about-component-copying/) to learn more.

## Available providers

* [CrowdStrike AIDR](/user-guide/access-policies/content-security/crowdstrike-aidr/) - Inspect MCP content with CrowdStrike AI Detection and Response (AIDR).
* [MCP Tool Access Control](/user-guide/access-policies/content-security/mcp-tool-access-control/) - Control which MCP tools an AI agent can discover and call.

An Access Policy can carry one of each at the same time. MCP Tool Access Control matches tool names first, so CrowdStrike AIDR inspects only the MCP tools and calls that MCP Tool Access Control allowed.

## Data shared for inspection

When an Access Policy includes CrowdStrike AIDR, Aembit sends the inspected MCP content to CrowdStrike AIDR, along with request metadata that identifies the request. Review CrowdStrike’s data handling before you add CrowdStrike AIDR to Access Policies that carry sensitive content. For exactly what Aembit sends, see [Data shared for inspection](/user-guide/access-policies/content-security/crowdstrike-aidr/#data-shared-for-inspection).

## Where Aembit records a provider’s decisions

Aembit records every decision a Content Security Provider makes, so you can confirm what a provider decided:

* [MCP workload events](/user-guide/audit-report/workload-events/supported-protocols/#content-security) record the decision for each MCP message under `application.mcp.contentSecurity`.
* [Access Authorization Events](/user-guide/audit-report/access-authorization-events/#content-security) name the provider that Aembit identified for the Access Policy.
* [Audit Logs](/user-guide/audit-report/audit-logs/) record when you create, update, or delete a provider, under the `ContentSecurity` category. An entry names who made the change, not which settings or MCP tool rules changed.

Each provider writes to its own field inside the `contentSecurity` element, so the field name identifies which provider acted: `crowdStrikeAidr` for CrowdStrike AIDR, and `aembitMcpToolsAcl` for MCP Tool Access Control.

To report on provider decisions in your own system, send workload events to a [log stream](/user-guide/administration/log-streams/).