# AI agent security at the gateway layer

URL: https://aiagentsecuritysolutions.com/layer-coverage-map/gateway/
Updated: 2026-11-16

Gateway coverage means a vendor documents a proxy or gateway between agents and models, tools or MCP servers that inspects and enforces policy on the traffic. On 16 Nov 2026, 13 of 16 vendors had a yes at the gateway layer, 2 had partial and 1 had none found. Levels are from vendor documentation, not lab tests.

## Gateway: every vendor

**Gateway by vendor**

| Vendor | Level | Note | Evidence |
|---|---|---|---|
| [Aim Security](/vendors/aim-security/) | Yes | Proxy, AI gateway or API integration points are documented. | [aim-security-49](/vendors/aim-security/#fact-aim-security-49), [aim-security-50](/vendors/aim-security/#fact-aim-security-50) |
| [Check Point](/vendors/check-point/) | Yes | Guard API and inline enforcement screen agent prompts, outputs and tool calls; native platform integrations are roadmap. | [check-point-22](/vendors/check-point/#fact-check-point-22), [check-point-23](/vendors/check-point/#fact-check-point-23) |
| [Cisco](/vendors/cisco/) | Yes | Kong plugin inspects LLM and MCP traffic; Cisco MCP gateway described as in development. | [cisco-05](/vendors/cisco/#fact-cisco-05), [cisco-07](/vendors/cisco/#fact-cisco-07), [cisco-41](/vendors/cisco/#fact-cisco-41) |
| [CrowdStrike](/vendors/crowdstrike/) | Yes | Falcon AI Gateway, included with Guardian, is generally available and drives the AI Kill Switch. | [crowdstrike-18](/vendors/crowdstrike/#fact-crowdstrike-18), [crowdstrike-23](/vendors/crowdstrike/#fact-crowdstrike-23), [crowdstrike-24](/vendors/crowdstrike/#fact-crowdstrike-24) |
| [Island](/vendors/island/) | Yes | Island MCP Gateway sits between agents and tools; LLM gateway and inference hook integrations. | [island-15](/vendors/island/#fact-island-15), [island-13](/vendors/island/#fact-island-13) |
| [Lasso Security](/vendors/lasso-security/) | Yes | Works with Kong, Envoy, TrueFoundry, Portkey and LiteLLM and ships an open-source MCP gateway. | [lasso-security-16](/vendors/lasso-security/#fact-lasso-security-16), [lasso-security-14](/vendors/lasso-security/#fact-lasso-security-14), [lasso-security-31](/vendors/lasso-security/#fact-lasso-security-31) |
| [Noma Security](/vendors/noma-security/) | Yes | Enforces through AI and MCP gateways, hooks, SDKs and APIs. | [noma-security-18](/vendors/noma-security/#fact-noma-security-18), [noma-security-19](/vendors/noma-security/#fact-noma-security-19) |
| [Operant AI](/vendors/operant-ai/) | Yes | MCP Gateway trust zones and AI Gatekeeper LLM gateway. | [operant-ai-21](/vendors/operant-ai/#fact-operant-ai-21), [operant-ai-22](/vendors/operant-ai/#fact-operant-ai-22) |
| [Palo Alto Networks](/vendors/palo-alto-networks/) | Yes | AI Gateway proxies LLM calls with inline guardrails; an MCP server tool scans tool calls. | [palo-alto-networks-41](/vendors/palo-alto-networks/#fact-palo-alto-networks-41), [palo-alto-networks-42](/vendors/palo-alto-networks/#fact-palo-alto-networks-42), [palo-alto-networks-45](/vendors/palo-alto-networks/#fact-palo-alto-networks-45) |
| [Pillar Security](/vendors/pillar-security/) | Yes | Runtime guardrails work with named AI gateways and any gateway via API. | [pillar-security-27](/vendors/pillar-security/#fact-pillar-security-27) |
| [SentinelOne (Prompt Security)](/vendors/sentinelone/) | Yes | MCP Gateway and enforcement at the AgentCore gateway. | [sentinelone-14](/vendors/sentinelone/#fact-sentinelone-14), [sentinelone-35](/vendors/sentinelone/#fact-sentinelone-35) |
| [WitnessAI](/vendors/witnessai/) | Yes | Network enforcement of an approved MCP server and tool list, plus REST API protection in the orchestration layer. | [witnessai-33](/vendors/witnessai/#fact-witnessai-33), [witnessai-34](/vendors/witnessai/#fact-witnessai-34), [witnessai-36](/vendors/witnessai/#fact-witnessai-36) |
| [Zenity](/vendors/zenity/) | Yes | MCP gateway URL with allow, modify or block of tool calls. | [zenity-24](/vendors/zenity/#fact-zenity-24), [zenity-25](/vendors/zenity/#fact-zenity-25) |
| [Microsoft](/vendors/microsoft/) | Partial | Open-source MCP Gateway and Agent 365 MCP tool real-time protection. | [microsoft-28](/vendors/microsoft/#fact-microsoft-28), [microsoft-39](/vendors/microsoft/#fact-microsoft-39), [microsoft-68](/vendors/microsoft/#fact-microsoft-68) |
| [Straiker](/vendors/straiker/) | Partial | Integrates with AI gateways; a Straiker gateway itself is not documented. | [straiker-19](/vendors/straiker/#fact-straiker-19), [straiker-20](/vendors/straiker/#fact-straiker-20), [straiker-21](/vendors/straiker/#fact-straiker-21) |
| [Bay](/vendors/bay/) | None found | No gateway or proxy product found; vendor says it uses no proxy. | [bay-44](/vendors/bay/#fact-bay-44), [bay-45](/vendors/bay/#fact-bay-45) |

## What agents run at the gateway layer

A gateway sits between applications or agents and the models, tools or MCP servers they call. CrowdStrike says developers connect an existing SDK or coding tool by changing the base URL to the gateway and using a gateway key. Check Point and Clalit Health Services announced on 1 October 2026 that they will jointly build a dedicated AI gateway between users, applications and AI models.

Sources: [Inside Falcon AI Gateway: One Control Point for AI Traffic](https://www.crowdstrike.com/en-us/blog/falcon-ai-gateway-one-control-point-for-ai-traffic/).

## What a control at the gateway layer can and cannot see

A gateway can see prompts, responses and usage on the traffic that reaches it, and can enforce one policy for managed and unmanaged devices. CrowdStrike says Falcon AI Gateway inspects prompts and responses and enforces policy across both.

It cannot see traffic that bypasses it, or what an agent does on a machine after a response arrives. CrowdStrike discussed keeping the request path short but gave no latency number or fail-open or fail-closed behavior in its post, so those remain open questions for buyers.

Sources: [Inside Falcon AI Gateway: One Control Point for AI Traffic](https://www.crowdstrike.com/en-us/blog/falcon-ai-gateway-one-control-point-for-ai-traffic/); [Clalit Health Services and Check Point announce a strategic partnership](https://www.checkpoint.com/press-releases/clalit-health-services-and-check-point-announce-strategic-partnership-to-secure-ai-adoption-across-healthcare-environments/).

## Who documents the gateway layer

Yes on 16 Nov 2026: Aim Security, Check Point, Cisco, CrowdStrike, Island, Lasso Security, Noma Security, Operant AI, Palo Alto Networks, Pillar Security, SentinelOne (Prompt Security), WitnessAI, Zenity.

Partial: Microsoft, Straiker.

None found: Bay.

## Related pages

- [The full Layer Coverage Map](/layer-coverage-map/)
- [Identity](/layer-coverage-map/identity/)
- [Endpoint](/layer-coverage-map/endpoint/)
- [Method](/layer-coverage-map/methodology/)
- [Vendor profiles](/vendors/)
