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 application programming interface (API) Security materials reviewed did not provide a public claim for authorization and control across agent, tool, Model Context Protocol (MCP), or connector handoffs.
No quoted source text is recorded for this claim.
Related framework references (5)
Salt claims controls that detect and address risky exposure in Model Context Protocol (MCP) and agent-to-agent (A2A) environments.
the riskiest exposures in MCP and A2A environments
Related framework references (5)
Imperva AI Application Security materials reviewed did not provide a public claim for authorization and control across agent, tool, Model Context Protocol (MCP), or connector handoffs.
No quoted source text is recorded for this claim.
Related framework references (5)
Kong claims control and observation of agent-to-agent communication over agent-to-agent (A2A).
Control and observe agent-to-agent communication over the A2A protocol
Related framework references (5)
Speakeasy claims distributed traces across agents, Model Context Protocol (MCP) servers, and downstream application programming interfaces (APIs).
Follow a tool call across agents, MCP servers, and downstream APIs
Related framework references (5)
Harness AI Security materials reviewed did not provide a public claim for authorization and control across agent, tool, Model Context Protocol (MCP), or connector handoffs.
No quoted source text is recorded for this claim.
Related framework references (5)
Wallarm claims access and schema controls for agent-to-Model Context Protocol (MCP) tool handoffs.
ensure tool calls conform to the published schema
Related framework references (5)
Cequence claims authentication and inline authorization of agent-to-tool and agent-to-application programming interface (API) handoffs.
full session, on every tool call
Related framework references (5)
Upwind materials reviewed did not provide a public claim for trust or policy enforcement between agents.
No quoted source text is recorded for this claim.
Related framework references (5)
Proofpoint materials reviewed did not provide a public claim for trust or policy enforcement between agents.
No quoted source text is recorded for this claim.
Related framework references (5)
Securiti AI materials reviewed did not provide a public claim for trust or policy enforcement between agents.
No quoted source text is recorded for this claim.
Related framework references (5)
Snyk Evo materials reviewed did not provide a public claim for trust or policy enforcement between agents.
No quoted source text is recorded for this claim.
Related framework references (5)
ModelOp materials reviewed did not provide a public claim for trust or policy enforcement between agents.
No quoted source text is recorded for this claim.
Related framework references (5)
LatticeFlow AI materials reviewed did not provide a public claim for trust or policy enforcement between agents.
No quoted source text is recorded for this claim.
Related framework references (5)
Runlayer materials reviewed did not provide a public claim for trust or policy enforcement between agents.
No quoted source text is recorded for this claim.
Related framework references (5)
Keycard claims authentication for agent-to-agent delegation while preserving user identity.
Announcing Keycard for Multi-Agent Apps
Related framework references (5)
AWS Bedrock native-control materials reviewed did not provide a public Model Context Protocol (MCP), agent-to-agent (A2A), or agent-to-agent communication security claim.
No quoted source text is recorded for this claim.
Related framework references (5)
Microsoft claims Entra Agent ID supports OAuth 2.0, Model Context Protocol (MCP), and agent-to-agent (A2A) for authentication and agent-to-agent communication.
supports standard protocols such as OAuth 2.0, MCP, and A2A for authentication and agent-to-agent communication.
Related framework references (5)
Zscaler claims AI Broker secures agentic communications through Model Context Protocol (MCP) and agent-to-agent (A2A) brokers with fine-grained access policies.
Secure agentic communications through MCP and A2A brokers and enforce fine-grained access policies across every enterprise AI agent.
Related framework references (5)
Palo Alto Networks says Portkey provides an AI Gateway for Prisma AIRS that can monitor, route, and secure AI transactions and supports agent-to-agent communication.
monitor, route, and secure every AI transaction across the enterprise.
Related framework references (5)