Benefits with Ory + Exa MCP Server
Use Cases
— 01 use caseAgent IAM
Support agents use Read for quick lookups, one research agent gets Write for billed jobs, Admin only matters for tools Exa adds later, and others get Block.
Core Functionality
— 04 capabilitiesRead, write, admin, or no access
Ory Agent Security classifies every tool on the Exa MCP server as read, write, or admin, so you can give each user, team, or agent type only the level it needs: read for everyday agents that search the web, write for research agents that run longer research jobs, and no access for agents handling confidential work.
Enforced before execution
Ory Agent Security checks each tool call against the user, the agent acting for them, and any sub-agent inside the agent harness, so a denied research job stops before it reaches Exa, with nothing to roll back and no gateway to deploy.
Observe, then enforce
Observe mode shows which agents depend on Exa and how heavily without blocking anything, so you can apply Ory's pre-built policy for the Exa MCP server and enforce it on your own schedule.
Complete audit trail
Every allow and deny decision on the Exa MCP server streams to your SIEM through OpenTelemetry with the user, agent, and action attached, so you can show which agent sent a query to Exa and for whom.