The control plane your AI agent operates.
Federated authorization, queryable from any AI agent.
Herald exposes EnforceAuth’s full authorization signal — decisions, audit, entities, policies, deployments, fleet — as MCP tools. Same RBAC as the human Console. Same audit log. Connect Claude Code, Cursor, Cline, or any MCP-capable client.
❯
Authorization is a question
you can finally ask out loud.
Herald is the third step of the EnforceAuth journey: once Zift extracted authz from your code and Writ governs it, Herald lets you interrogate it.
Authorization data was a silo.
Decision logs lived in a SIEM nobody opened, audit logs in a vault nobody read, RBAC matrices in a Confluence page from 2023. Cross-cutting questions — “Did anyone who left this quarter still have prod access?” — meant a Jira ticket and three engineers.
Herald federates it.
An MCP tool surface over EnforceAuth’s full authorization signal — decisions, audit, entities, policies, deployments, fleet. Same RBAC as the human Console. Same audit log. Connect any AI agent: Claude Code, Cursor, Cline, your own.
Join it to the rest of your business.
Your IdP, HRIS, data warehouse, tickets, SIEM, and CRM already expose MCP servers. Herald is one more peer in that mesh. An agent can ask a question that crosses all of them in one prompt — and the answer becomes a Slack reply, a Jira ticket, a SOC 2 export.
Eighteen prompts that didn’t fit in last quarter’s access review.
None of these would have shipped as a feature. They’re questions, not products. Herald lets the agent assemble each one on demand.
Every prompt above runs against shipped MCP tools today · entries are illustrative phrasings, not canned templates.
Herald is one peer. You bring the rest.
EnforceAuth doesn’t host these connectors. You point your agent at Herald and at whichever MCP servers your stack already exposes — the agent does the join.
Identity & HRIS
SCM & build
Data warehouse
ITSM & on-call
CRM & commerce
SIEM & cloud audit
Herald alone covers a lot.
Pair it with four MCP peers — unlock four more domains.
Each combo below pairs Herald with one or two of the connector categories above. None require new EnforceAuth integration work — the agent assembles the join at runtime.
MCP’s value compounds: every peer the customer adds becomes a join Herald can participate in — no extra integration work on our side. We bring the authorization signal; the rest of the stack provides the business context.
Point your agent at Herald.
Ask it the question.
Herald is live on every paid tenant. Free tier gets a read-only OAuth scope for evaluation. Connect Claude Code, Cursor, Cline, or any MCP-capable client.
