Public-source research
Vendor evidence
Review what vendors say publicly, the exact quoted source text, the security requirement each statement may support, and what still needs verification.
Research library coverageCounts describe the research workflow, not vendor quality or product effectiveness.View details
Evidence records1280
Source checked863
Needs verification0
Source captured0
No supporting claim found411
Excluded from evidence6
Akamai Firewall for AI offers edge or REST application programming interface (API) integration for AI-application protection.
Integrate via the Akamai edge or REST API for seamless protection across AI applications.
Related framework references (5)
Salt claims default Model Context Protocol (MCP) guardrails that enforce safe AI-agent behavior.
built-in guardrails, enabled by default, enforce safe agent behavior automatically
Related framework references (5)
Imperva claims inline AI guardrails through a software as a service (SaaS) reverse proxy between applications and large language models (LLMs).
operates as a SaaS reverse proxy positioned between your applications and Large Language Models
Related framework references (5)
Kong claims one governance layer across large language model (LLM) calls, Model Context Protocol (MCP) tool access, application programming interface (API) traffic, events, and agent-to-agent (A2A) communication.
single governance layer across the entire stack
Related framework references (5)
Speakeasy claims SSO, role-based access, and runtime guardrails at its Model Context Protocol (MCP) gateway.
SSO, RBAC, and runtime guardrails at the gateway
Related framework references (5)
Harness claims runtime AI guardrail policies and blocking for protected AI applications.
Create policies to enforce best practices for AI usage
Related framework references (5)
Wallarm claims Model Context Protocol (MCP) policies that enforce access, validate request parameters, check tool schemas, and block by IP or session.
enforce access policies, validate request parameters, and ensure tool calls conform to the published schema
Related framework references (5)
Cequence claims inline policy enforcement for every tool call across a full agent session.
enforces policy inline in the request path
Related framework references (5)
Upwind claims Model Context Protocol (MCP) runtime tracing of prompts, decision chains, tool calls, file actions, application programming interfaces (APIs), and cloud interactions.
MCP Security brings agentic visibility to runtime by tracing AI-driven actions end-to-end.
Related framework references (5)
Proofpoint claims authentication, content inspection, and approved-server registry controls at the Model Context Protocol (MCP) boundary.
enforces authentication and content inspection at the MCP boundary
Related framework references (5)
Securiti AI materials reviewed did not provide a public claim for inline model, agent, tool, application programming interface (API), or Model Context Protocol (MCP) policy enforcement.
No quoted source text is recorded for this claim.
Related framework references (5)
Snyk Evo materials reviewed did not provide a public claim for inline model, agent, tool, application programming interface (API), or Model Context Protocol (MCP) policy enforcement.
No quoted source text is recorded for this claim.
Related framework references (5)
ModelOp materials reviewed did not provide a public claim for inline model, agent, tool, application programming interface (API), or Model Context Protocol (MCP) policy enforcement.
No quoted source text is recorded for this claim.
Related framework references (5)
LatticeFlow AI materials reviewed did not provide a public claim for inline model, agent, tool, application programming interface (API), or Model Context Protocol (MCP) policy enforcement.
No quoted source text is recorded for this claim.
Related framework references (5)
Runlayer claims an approved Model Context Protocol (MCP) catalog and governed Model Context Protocol (MCP) gateway across major AI clients.
serve them through a governed MCP gateway across every major AI client
Related framework references (5)
Keycard claims authentication and task-scoped access controls for Model Context Protocol (MCP), CLI, application programming interface (API), and downstream services.
Add auth to any agent surface - MCP, CLI, or API.
Related framework references (5)
Palo Alto Networks claims centralized control of tool calls, large language model (LLM) interactions, and Model Context Protocol (MCP) connections with granular runtime policy enforcement.
Gain centralized control of tool calls, LLM interactions, and Model Context Protocol (MCP) connections — enforcing granular policies on how agents interact with systems.
Related framework references (5)
Cisco claims real-time Model Context Protocol (MCP) enforcement, tool allowlists and blocklists, and runtime policies across prompts, responses, agent actions, and tool calls.
MCP runtime enforcement: Monitor and enforce safe behavior across MCP requests and responses connecting LLMs, agents, and tools.
Related framework references (5)
Microsoft Foundry claims preview Model Context Protocol (MCP) governance by routing eligible tool traffic through an AI Gateway where Azure application programming interface (API) Management policies enforce authentication, rate limits, IP restrictions, and audit logging.
An AI gateway provides a single, governed entry point where you can enforce authentication, rate limits, IP restrictions, and audit logging
Related framework references (5)
CrowdStrike Falcon AIDR claims real-time protection for prompts, responses, agent actions, Model Context Protocol (MCP) servers, and AI/application programming interface (API) gateways with policy enforcement and automated response.
Falcon AIDR secures every prompt, response, and agent action in real time.
Related framework references (5)