Validated IdP claims
MCP access should carry validated IdP claims before a tool call is allowed, whether the token represents an agent, workload, user, or delegated session.
AI agent governance
Connect MCP to Entra ID, Okta, or Your Enterprise IdP
Datawiza Agent Gateway validates agent access tokens, applies MCP server and tool-level policies, and logs every decision before agents reach sensitive tools.
For MCP teams
MCP needs enterprise access control, not just connectivity
MCP makes tools easy for agents to discover and call. That becomes risky when servers expose SaaS data, internal APIs, databases, tickets, code repositories, or business workflows.
The core question: which user, which agent, which tool, which action, under which policy?
Tool permissions
One MCP server may expose read, write, export, and admin-style tools. Access needs to be checked at the tool and action level.
Audit trail
Security teams need proof of who called which tool, what policy applied, and what happened next.
Gateway pattern
Put token validation, policy, and audit in front of MCP tools
Datawiza Agent Gateway sits between agents and MCP servers. Agents authenticate with your enterprise IdP, send their access token to the gateway, and Datawiza validates the token before applying tool-level policy.
Enterprise IdP integration
Let agents authenticate with Microsoft Entra ID, Okta, Ping, AWS IAM, or another IdP, then present signed access tokens to Datawiza for validation.
Tool-level access control
Decide which users, groups, agents, environments, MCP servers, tools, and actions are allowed for each workflow.
Token validation and audit
Validate issuer, audience, signature, expiry, scopes, and claims, then capture user, agent, tool, policy, and outcome for audit.
Architecture
A Gateway Between Agents and MCP Servers
Agent traffic flows through Datawiza before it reaches MCP servers. Validated IdP claims and policy become part of every tool-call decision.
Step 1
Agent or MCP client
Authenticates with Entra ID, Okta, or another IdP and receives a signed access token.
Step 2
Datawiza Agent Gateway
Validates issuer, audience, signature, expiry, scopes, and claims, then checks MCP server, tool, and action policy.
Step 3
MCP servers and tools
Receive only approved MCP requests. Denied, approved, and approval-routed decisions are logged.
Identity providers
Entra IDOktaPingAWS IAMOAuth / OIDC
Deployment options
Azure / AWS / Google CloudOn-premises / private networkDatawiza-hosted service
Token validation: trust the IdP token only after Datawiza verifies it.
Tool policy: allow or deny by agent, claim, MCP server, tool, action, and environment.
Audit: record who or what called the tool, which policy matched, and the outcome.
Workflow
How enterprise MCP access control works
Start with one MCP server and one agent workflow. Prove the token validation, policy, and audit path before expanding to more tools.
- 1Route MCP traffic through DatawizaPoint the MCP client or agent workflow at the Datawiza gateway endpoint instead of a direct MCP server URL.
- 2Validate the token and enforce policyValidate the enterprise IdP access token, then evaluate the user, agent, server, tool, and action.
- 3Forward requests and record the decisionForward approved MCP requests and log denied, approved, or approval-routed decisions.
Comparison
Direct MCP access vs. Datawiza Agent Gateway
Area
Direct MCP connectivity
With Datawiza Agent Gateway
Access path
Agents connect directly to MCP servers
Agents present enterprise IdP tokens to one gateway
Authorization
Authorization varies by MCP server
Policy checks the user, agent, server, tool, action, and environment
Token handling
Tokens and API keys can spread into local configs
Gateway validates enterprise IdP tokens before MCP tools run
Audit
Logs are split across clients, servers, and tools
Every tool call records identity, policy, decision, and outcome
Policy examples
Make MCP policy concrete
Group-based tool access
Finance users can read invoices. Finance managers can approve payments. Contractors cannot call export tools.
Action-level guardrails
Allow read-only CRM lookup, but require approval before bulk exports or destructive updates.
Audit-ready evidence
Send MCP access logs to your SIEM with user identity, agent, server, tool, action, decision, and result.
Next step
Want to enforce MCP access with your enterprise IdP?
Bring one MCP server, one agent workflow, and your IdP token requirements. We can map where token validation, policy, and audit should sit before you roll out MCP broadly.