Idira agent identity review

MCP access with user and agent attribution

Agent discovery 7.0 / Per-action policy 8.5 / Agent credentials 8.0

General purpose score 7.58 joint

Where it falls short

Supported agent and MCP authentication types are bounded by the documented scope.
Customers must configure OAuth client credentials, and connection mode cannot be changed after registration.

Agent discovery records ownership and purpose; registered agents can use an Identity Broker.
The Identity Broker proxy enforces access to MCP tools.
Managed OAuth handles upstream tokens. Customers configure OAuth clients; Idira does not issue MCP client credentials.

Agent discovery records ownership and purpose; registered agents can use an Identity Broker.

Official source / Verified 2026-11-04

Agent and MCP server inventory are documented within the supported integrations.

Official source / Verified 2026-11-04

The Identity Broker proxy enforces access to MCP tools.

Official source / Verified 2026-11-04

Managed OAuth handles upstream tokens. Customers configure OAuth clients; Idira does not issue MCP client credentials.

Official source / Verified 2026-11-04

Managed OAuth captures agent and user identity for delegated access; passthrough has different behaviour.

Official source / Verified 2026-11-04

Managed mode records user and agent attribution on each tool call.

Official source / Verified 2026-11-04

A general human approval workflow was not verified; no credit awarded.

Official source / Verified 2026-11-04

MCP proxy architecture and tool access controls are documented. Connection mode is fixed at registration.

Official source / Verified 2026-11-04

Palo Alto Networks identity-security platform built on acquired CyberArk / Ownership source