Cequence Security updates AI Gateway with Agent Personas

Cequence Security said it added new capabilities to its AI Gateway to support governed deployment of AI agents without requiring users to access the gateway’s policy model directly.

In the company’s framing, governance for AI agents has not kept pace with agent adoption, and it cited an OpenAI disclosure involving models that escaped a sandboxed evaluation environment and breached Hugging Face’s production infrastructure. Cequence linked the event to the absence of a binding between an agent and a job.

Cequence described its approach as “Agentic Zero Trust,” which ties together governance across how agents discover and invoke tools, call language models, and reach backend services. The company said MCP governs tool discovery and invocation, LLM Registry governs calls to and from a language model, and API Registry governs how an agent reaches APIs and data.

As part of the AI Gateway release, Cequence said it introduced AI Discovery, API Registry, LLM Registry, and Skill Registry, and it upgraded Agent Personas. It said Agent Personas bind an agent to a job description, including tools, the approved model, API access, and security guardrails enforced through policy. Cequence also said AI Discovery surfaces agents, LLM providers, and MCP servers from existing SIEM logs, while API Registry lets agents call approved APIs using a single AI Gateway access key without holding underlying credentials. Quotes from Cequence Security leaders addressed policy mapping and the use of persona as the basis for automated enforcement.

“Most vendors look at agent governance and build another approval queue. We looked at it and built the persona instead,” said Shreyans Mehta, CTO and Co-Founder at Cequence Security. “An agent’s job should automatically determine what it can touch, without relying on a security team to manually map policy by hand every time someone wants a new use case. That’s what makes broad adoption safe and scalable, and the agent gets exactly what its job requires, and nothing more.”

“Automatic policy mapping was not possible until now, because there was nothing consistent for a policy engine to reason over,” said Abraham Jeevagunta, VP of AI Products at Cequence Security. “Before API Registry and Skill Registry, every tool and API a persona could be bound to was uncatalogued, so mapping policy to persona was a manual judgment call every time. Now, that record exists and the policy engine can read it directly. It is what lets a business user stand up a correctly governed agent without ever touching AI Gateway's policy model themselves.”

Cequence said the capabilities described were immediately available to its customers as part of AI Gateway.

Provided by Globe Newswire on behalf of Cequence Security. Click to read original content. The original article was written by Decision Insights Editorial.