Benefits with Ory + JetBrains MCP Server
Use Cases
— 01 use caseAgent IAM
Reviewers read code at Read, coding agents refactor at Write, the agent that builds and runs commands gets Admin, and Block keeps others out of the IDE.
Core Functionality
— 04 capabilitiesRead, write, admin, or no access
Ory Agent Security classifies every tool on the JetBrains MCP server as read, write, or admin, so you can give each user, team, or agent type only the level it needs: read for analysis agents, write for coding agents that edit files, admin for agents you'd trust with a terminal, and no access for agents outside the coding workflow.
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 terminal command stops before it reaches the IDE, with nothing to roll back and no gateway to deploy.
Observe, then enforce
Observe mode shows which agents edit files or run commands through the IDE without blocking anything, so you can apply Ory's pre-built policy for the JetBrains MCP server and enforce it on your own schedule.
Complete audit trail
Every allow and deny decision on the JetBrains MCP server streams to your SIEM through OpenTelemetry with the user, agent, and action attached, so you can show which agent ran a command on a user's machine.