Benefits with Ory + Sentry MCP Server
Use Cases
— 01 use caseAgent IAM
Debuggers read at Read, triage agents work issues at Write, keys and alert rules stay at Admin, and Block shuts out agents with no Sentry work.
Core Functionality
— 04 capabilitiesRead, write, admin, or no access
Ory Agent Security classifies every tool on the Sentry MCP server as read, write, or admin, so you can give each user, team, or agent type only the level it needs: read for debugging agents, write for triage agents, admin for platform owners' agents, and no access for agents with no role in error handling.
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 project change stops before it reaches Sentry, with nothing to roll back and no gateway to deploy.
Observe, then enforce
Observe mode shows which agents query or update Sentry and for whom without blocking anything, so you can apply Ory's pre-built policy for the Sentry MCP server and enforce it on your own schedule.
Complete audit trail
Every allow and deny decision on the Sentry MCP server streams to your SIEM through OpenTelemetry with the user, agent, and action attached, so you can show which agent resolved an issue or changed alerting, and on whose behalf.