threatdeck
Live 13:45 UTC ·

MCP allowlist generator

Pick the MCP servers your organisation approves, check what MCP Server Watch knows about each one, and copy a pinned allowlist for each client. Launch commands pin the registry version, raised to the fixed release when a published advisory affects it.

1. Pick servers

    2. Add your own (internal servers)

    3. Copy the policy for each client

    Pick at least one server or add your own to fill these files.

    Claude Code: allowlist in managed settings

     
    • Merge these keys into managed-settings.json (or MDM / the claude.ai admin console). allowManagedMcpServersOnly makes this the only allowlist, so users cannot broaden it; deniedMcpServers still merges from every scope. source
    • A stdio server loads only if its command and every argument match a serverCommand entry exactly, in order (env is not compared). A remote server must match a serverUrl entry. Generated commands are a starting point: add any arguments a server needs (paths, docker -e flags) so the entry matches the configs your developers use. source
    • An empty list blocks every server users add. The lock is read across managed sources from Claude Code v2.1.273.

    Claude Code: exclusive server set (managed-mcp.json)

     
    • Alternative to the allowlist: Claude Code then loads only these servers, and users cannot add others. Deploy to /Library/Application Support/ClaudeCode/ (macOS), /etc/claude-code/ (Linux, WSL) or C:\Program Files\ClaudeCode\ (Windows); not deliverable through server-managed settings. source
    • Any user on the machine can read the file: do not put API keys in env blocks; use ${VAR} expansion, OAuth or headersHelper. Add arguments or env your servers need before deploying.

    GitHub Copilot (CLI, VS Code, Copilot app, JetBrains, cloud)

     
    • Add allowedMcpServers to your enterprise managed settings: .github-private repository copilot/managed-settings.json, MDM, or /Library/Application Support/GitHubCopilot/ · /etc/github-copilot/ · %ProgramFiles%\GitHubCopilot\. The MCP servers in Copilot policy must be enabled; set Restrict MCP access to registry servers to Allow all to avoid conflicts. source
    • Built-in servers such as the GitHub MCP server are always allowed. Servers whose URL or command still contains a variable such as ${VAR} are blocked. With several sources, a server must match the allowlist at every layer that defines one. source
    • VS Code reads these enterprise managed settings; from VS Code 1.145 the allowlist takes precedence over registry-only access. The VS Code device policy chat.mcp.access set to none still disables MCP entirely. source

    Cursor (Enterprise team dashboard)

     
    • Cursor has no policy file for this: paste each line as a command or URL entry under MCP Configuration in the team dashboard (Enterprise). Command entries match the full command string; the leading * matches the runner at any install path. source
    • Adding a server to the allowlist does not install it on users' machines. Per-server tool lists and network modes are set in the same dashboard.

    Generic CSV (review, ticketing, other tools)

     
    • One row per entry with pinned version, ThreatDeck advisories and signals.

    Generic JSON

     
    • The same list as JSON, with serverUrl / serverCommand entries per server.

    Full Claude Code policy (secrets, sandbox, hooks lock)? Claude Code managed settings generator · GitHub Copilot managed settings · Playbook: lock down MCP

    Following

    Follow the vendors, products, AI tools, techniques and actors you care about. Matching stories, CVEs and exploited bugs are marked, a Following tab appears in the feed, and returning visits show what changed. Saved only in this browser.

    Presets

    Get updates

    A personal RSS feed of new stories on everything you follow. Paste it into any feed reader, Slack or Teams RSS app.