Benefits with Ory + Google Cloud MCP Server
Use Cases
— 01 use caseAgent IAM
Reporting agents at Read, build agents at Write, the few that change IAM or run gcloud at Admin, and Block for agents with no cloud work.
Core Functionality
— 04 capabilitiesRead, write, admin, or no access
Ory Agent Security classifies every tool on the Google Cloud MCP server as read, write, or admin, so you can give each user, team, or agent type only the level it needs: read for agents looking up projects and resources, write for operations agents that create and adjust resources, admin for platform owners' agents, and no access for agents with no reason to reach Google Cloud.
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 IAM policy change stops before it reaches Google Cloud, with nothing to roll back and no gateway to deploy.
Observe, then enforce
Observe mode shows which agents change resources or run commands and on whose behalf without blocking anything, so you can apply Ory's pre-built policy for the Google Cloud MCP server and enforce it on your own schedule.
Complete audit trail
Every allow and deny decision on the Google Cloud MCP server streams to your SIEM through OpenTelemetry with the user, agent, and action attached, so you can show which agent changed access or deleted a resource, and for whom.