Answer: To allow only approved MCP servers in Codex, start with deny-all using an empty managed table, then add approved servers by exact URL or executable/arguments so that Codex enables only servers whose configured name and identity match the enterprise-approved list. Status: Confirmed Entry: tool/codex/permissions-and-security/allow-only-approved-mcp-servers Revision: 2 Digest: sha256:b3f5c8d320995411 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:50:24Z Last changed: 2026-11-19T13:29:02Z (rollback: — → deploy an empty `mcp_servers` table) Last verified: 2026-11-20T13:38:35Z Next check: 2026-11-21T13:38:35Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of deny-all configuration | [mcp_servers] | [1] | 2026-11-20 matching rule | Codex enables only MCP servers whose configured name and identity match the enterprise-approved list. | [1] | 2026-11-20 HTTP server example | identity = { url = "https://mcp.example.com/docs" } | [1] | 2026-11-20 stdio matcher scope | The structured matcher checks the executable, argument count, and argument order. | [1] | 2026-11-20 deployment method | Store the approved list in a reviewed configuration repository and deploy it through admin-enforced requirements. | [1] | 2026-11-20 rollback | deploy an empty `mcp_servers` table | [1] | 2026-11-20 Sources: [1] OpenAI. "Codex security cookbook". https://learn.chatgpt.com/docs/enterprise/security-cookbook.md Role: primary. Accessed: 2026-11-20T13:38:35Z Quote: "Start with deny-all. An empty managed table disables all MCP servers: ```toml [mcp_servers]" (Supports: deny-all configuration) Quote: "Codex enables only MCP servers whose configured name and identity match the enterprise-approved list." (Supports: matching rule) Quote: "identity = { url = "https://mcp.example.com/docs" }" (Supports: HTTP server example) Quote: "The structured matcher checks the executable, argument count, and argument order." (Supports: stdio matcher scope) Quote: "Store the approved list in a reviewed configuration repository and deploy it through admin-enforced requirements." (Supports: deployment method) Quote: "To stop all MCP usage immediately, deploy an empty `mcp_servers` table." (Supports: rollback) Snapshot SHA-256: bd59a6b1e051756cc5174ba6dad0c24b937039ee3450b8f48a48a4c4563db12e (captured 2026-11-19T13:29:01Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-19T13:29:02Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:38:35Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:38:35Z Last attempt: 2026-11-20T13:38:35Z Notes and limitations: Extracted automatically from a single official source (section "Allow only approved MCP servers"). Related: https://latestn.com/tool/codex/permissions-and-security/allowed-http-methods Which HTTP methods can I allow for Codex Cloud (Legacy) agent internet access? https://latestn.com/tool/codex/permissions-and-security/api-key-auth-automation How do I authenticate Codex in automation using an API key? https://latestn.com/tool/codex/permissions-and-security/approval-policies-sandbox-modes How do I configure approval policies and sandbox modes in Codex? https://latestn.com/tool/codex/permissions-and-security/act-on-security-findings What should I do with the findings from a Codex security change review? https://latestn.com/tool/codex/permissions-and-security/add-deployment-context-threat-model How do I add deployment context to a Codex threat model for validation? https://latestn.com/tool/codex/permissions-and-security/agent-security-requirements-work-cloud What are the Agent Security requirements for Local computer access with Work Cloud in Codex? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T13:29:02Z | changed | rollback: — → deploy an empty `mcp_servers` table | [1] 2026-11-19T13:29:02Z | changed | stdio matcher scope: — → The structured matcher checks the executable, argument count, and argument order. | [1] 2026-11-19T13:29:02Z | changed | HTTP server example: — → identity = { url = "https://mcp.example.com/docs" } | [1] 2026-11-19T13:29:02Z | changed | plugin-bundled servers: plugins..mcp_servers. → — | [1] 2026-11-19T13:29:02Z | changed | matching rule: The client enables a server only when both its name and identity match an approved entry. → Codex enables only MCP servers whose configured name and identity match the enterprise-approved list. | [1] 2026-11-19T13:29:02Z | changed | stdio server identity: command = { executable = "/usr/local/bin/company-mcp", args = [ → — | [1] 2026-11-19T13:29:02Z | changed | HTTP server identity: identity = { url = "https://mcp.example.com/docs" } → — | [1] 2026-11-13T03:50:24Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/permissions-and-security/allow-only-approved-mcp-servers/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/codex/permissions-and-security/allow-only-approved-mcp-servers POST: https://latestn.com/dispute/tool/codex/permissions-and-security/allow-only-approved-mcp-servers with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/permissions-and-security/allow-only-approved-mcp-servers?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I allow only approved MCP servers in Codex? Revision 2, last verified 2026-11-20T13:38:35Z. https://latestn.com/tool/codex/permissions-and-security/allow-only-approved-mcp-servers (accessed 2026-11-21T10:06:18Z). @misc{LatestN_tool_codex_permissions_and_security_allow_only_approved_mcp_servers_r2, title = {How do I allow only approved MCP servers in Codex?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/permissions-and-security/allow-only-approved-mcp-servers}}, note = {Revision 2; digest sha256:b3f5c8d320995411; last verified 2026-11-20T13:38:35Z; accessed 2026-11-21T10:06:18Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/codex/permissions-and-security/allow-only-approved-mcp-servers