
Or Weis
Announcing Permit MCP Gateway
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.


Featured Stories

Or Weis
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.

Gabriel L. Manor
The new Permit.io CLI brings developer-first workflows to access control. Define, test, deploy, and enforce fine-grained authorization using AI, CI/CD, GitOps, and OpenAPI — all from your terminal

Gabriel L. Manor
Coding agents execute code, run commands, and call APIs — not just generate text. This guide covers the real security risks, why authorization must happen at the tool-call level, and how Permit.io and the Permit MCP Gateway enforce least-privilege access for agentic workflows.

Or Weis
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.

Or Weis
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.

Or Weis
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.

Or Weis
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.

Or Weis
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.

Or Weis
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.

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

Or Weis
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.

Or Weis
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.

Or Weis
Secure MCP authorization with OAuth 2.1, zero standing permissions, and fine-grained access control for AI agents using Permit.io and agent.security.

Or Weis
The OpenAI–Mixpanel incident did not leak prompts or API keys, but it still exposed valuable metadata about API users. This post explains why metadata breaches in SaaS and GenAI ecosystems are so dangerous, and how to harden your stack with better governance and fine-grained authorization.