Benefits with Ory + Google Chrome DevTools MCP Server
Use Cases
— 01 use caseAgent IAM
Page inspectors work at Read, test agents click through flows at Write, script runners get Admin, and you set Block on agents that never need a browser.
Core Functionality
— 04 capabilitiesRead, write, admin, or no access
Ory Agent Security classifies every tool on the Chrome DevTools 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 that inspect pages, write for test agents that click and type through flows, admin for agents you'd trust with your own browser session, and no access for agents with no reason to drive a browser.
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 script run stops before it reaches Chrome, with nothing to roll back and no gateway to deploy.
Observe, then enforce
Observe mode shows which agents drive the browser or run scripts and for which users without blocking anything, so you can apply Ory's pre-built policy for the Chrome DevTools MCP server and enforce it on your own schedule.
Complete audit trail
Every allow and deny decision on the Chrome DevTools MCP server streams to your SIEM through OpenTelemetry with the user, agent, and action attached, so you can show which agent acted in a browser session and on whose behalf.