Identity-aware proxy positioned in front of MCP servers and APIs so that users and agents authenticate through an existing IdP before any tool call proceeds. Product material describes filtering tools/list discovery and gating tools/call invocation by policy; the fetched documentation site provides only high-level confirmation of that scope.
commercial · generally available · Research snapshot 2026-09-06
Show me Datawiza filtering the tools/list response for a low-privilege group and denying a tools/call write action after validating the Entra ID token claims.
Capabilities and evidence
Support labels reflect the supplied research. Documentation and vendor claims are not independent product tests. “Not established” means the researcher did not find support; it does not prove a capability is absent.
Vendor claim
The product page states users and agents sign in through the organisation's IdP before any request reaches an MCP server, with token issuer, audience, signature, expiry, scopes and claims validated.
Limit: Claim appears on a product page; no reference documentation for the validation pipeline was fetched.
Policy can filter which tools each identity discovers via tools/list and enforce which tools or actions it may invoke via tools/call, evaluating agent, claim, server, tool, action and environment.
Limit: Policy language, evaluation order and failure behaviour are not documented on the fetched pages.
Datawiza's documentation site describes the product as an identity-aware proxy and enterprise gateway for AI agents accessing tools, MCP and APIs, delivered cloud-native and cloud-managed.
Limit: The documentation landing page confirms scope but not specific enforcement features.