Benefits with Ory + Azure DevOps MCP Server
Use Cases
— 01 use caseAgent IAM
Reviewers read at Read, planning agents edit at Write knowing it can commit files, pipeline work stays at Admin, and Block covers the rest.
Core Functionality
— 04 capabilitiesRead, write, admin, or no access
Ory Agent Security classifies every tool on the Azure DevOps MCP server as read, write, or admin, so you can give each user, team, or agent type only the level it needs: read for planning and reporting agents, write for agents that update work items and contribute code, admin for a release agent, and no access for agents with no role in your delivery process.
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 pipeline run stops before it reaches Azure DevOps, with nothing to roll back and no gateway to deploy.
Observe, then enforce
Observe mode shows which agents touch boards, repos, and pipelines and on whose behalf without blocking anything, so you can apply Ory's pre-built policy for the Azure DevOps MCP server and enforce it on your own schedule.
Complete audit trail
Every allow and deny decision on the Azure DevOps MCP server streams to your SIEM through OpenTelemetry with the user, agent, and action attached, so you can show which agent started a pipeline or changed code, and for whom.