API key permissions and MCP usage analytics
Choose who can create API keys
API keys give programmatic access to MCPs, so not every member needs to create them. The permission to create API keys is no longer enabled by default for regular members, and you can enable it for custom roles to control who can use it.
- Create custom roles with the "Create API key" permission so that team members who need it (e.g., engineers) can do so. This is only needed when using MCPs via programmatic interfaces.
- Review any API keys created on your enterprise settings page.
- More details: Roles and permissions, custom roles.
Docs: Roles and permissions
Find out who uses which MCPs, from your agent
Usage questions like who uses which MCPs used to mean exporting logs and building a report. The Admin MCP server now comes with new tools, including the ability to query MCP and agent monitor logs.
If you're trying to figure out who is using which MCPs, or which MCPs are most popular in the organization, you can use these tools with your agent to get the analysis you need.
Docs: Admin MCP
Also in this release
More MCP admin tools
The Admin MCP server can also manage connectors, enable and disable tools, create bundles, and manage middleware rules.
Codex agent monitor
Agent Monitor now integrates with OpenAI's Codex.
Guardrails
We've changed the UI for applying guardrails and middleware to the agent monitor and MCP gateway. Middleware, including middleware that calls out to your DLP, can be attached to the agent monitor so that hooks in Claude, Cursor, and Codex call out to it.