Or Weis

Microsoft Entra Agent ID and SD-JWT agent identity solve registration, governance, and authentication — but they don't decide whether a specific MCP tool call is permissible right now. This article explains the gap and the runtime authorization architecture needed to close it.

AI agents acting on behalf of users need more than authentication — they need governance. This article covers the Permit.io agentic identity model, policy-as-code lifecycle, MCP Gateway enforcement, zero standing credentials, Guardian Agents, and what an audit trail must contain to be meaningful.

AI agents acting across tools, APIs, and multi-agent pipelines raise hard questions about identity, authentication, and authorization. This article covers agentic identity (delegating human + workflow context + intent), agent interrogation, SPIFFE, OAuth token exchange, least privilege at runtime, and what audit actually means for agentic systems.

AI agents break the traditional least-privilege model. This article explains why, defines agentic identity (delegating human + workflow context + declared intent), and shows how Permit.io enforces zero standing privileges through gateway-vaulted credentials, the PDP, MCP Gateway, and downscoped delegation chains.

RBAC is useful for coarse AI agent guardrails, but ReBAC is needed for delegated, tenant-aware, resource-level authorization. Learn when to use RBAC, ReBAC, and both for secure agentic systems.

MCP auth is necessary, but it is not the same thing as agent authorization. If you want secure agent systems, you need identity, delegation, policy, and runtime enforcement beyond OAuth.

If you are comparing an MCP gateway to a basic MCP proxy, the real difference is not routing. It is identity, authorization, consent, auditability, and runtime control for agent actions.

A practical review guide for security, privacy, and procurement teams evaluating whether an MCP gateway can meet SOC 2, HIPAA, and privacy requirements — with concrete examples from Permit MCP Gateway.

A practical blueprint for securing Model Context Protocol (MCP) agents across identity, consent, policy, and audit layers without rewrites.

Announcing Permit MCP Gateway, a new trust and enforcement layer for MCP that brings identity, consent, fine-grained authorization, auditability, and runtime control to AI agent actions.

Traditional auth breaks for AI agents. Learn how to secure delegation and consent with purpose-bound, goal-scoped permissions, and how agent.security (powered by Permit.io) enforces it fast.

RBAC breaks down in modern SaaS, multi-tenant, and AI-driven systems. Learn why RBAC alone is insufficient, how ABAC and ReBAC solve real-world access control challenges, and how to evolve your authorization model without a rewrite.