Benefits with Ory + HubSpot MCP Server
Use Cases
— 01 use caseAgent IAM
Reporting agents read at Read, sales agents edit deals at Write, pipeline and property changes stay at Admin, and Block keeps the rest out of the CRM.
Core Functionality
— 04 capabilitiesRead, write, admin, or no access
Ory Agent Security classifies every tool on the HubSpot MCP server as read, write, or admin, so you can give each user, team, or agent type only the level it needs: read for sales and support agents looking up records, write for CRM agents that update records, admin for operations owners' agents, and no access for agents with no role in sales, marketing, or service.
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 bulk update stops before it reaches HubSpot, with nothing to roll back and no gateway to deploy.
Observe, then enforce
Observe mode shows which agents change CRM records and on whose behalf without blocking anything, so you can apply Ory's pre-built policy for the HubSpot MCP server and enforce it on your own schedule.
Complete audit trail
Every allow and deny decision on the HubSpot MCP server streams to your SIEM through OpenTelemetry with the user, agent, and action attached, so you can show which agent changed a deal or contact, and for which user.