By Vero SecurityBuilt and funded by Vero Security, the AI Security Engineering platform.Read the charter

MCP server and tool allowlists

Client-side controls decide which MCP servers can start and which of their tools may run without approval. Claude Code, Codex, Gemini CLI, Cursor and GitHub Copilot all support allowlists by server or tool, and some match on server identity, not just name. Enterprise allowlists stop users from wiring in arbitrary servers from the internet.

Read in this order

  1. OfficialClaude Code: Control MCP server access for your organizationStart here: how to lock down which MCP servers an org allows.
  2. OfficialCodex: Managed configuration (MCP allowlist)Codex's MCP allowlist inside its managed configuration.
  3. OfficialGitHub: Restrict MCP server access to a custom registryRestricting Copilot to a custom MCP registry, step by step.

Save your progress

We email you a sign-in link. No password.

By signing in you agree to the terms. The privacy policy explains how we use your details.

Join the AI security engineering community

Free. Roadmap updates, chapters near you, and first word when credentials open.

We’ll email you community updates. Unsubscribe anytime. By sending this you agree to the terms. The privacy policy explains how we use your details.