MCP Server Security

MCP security checklist: respond

Six steps cover a bad or vulnerable server: remove it everywhere, rotate credentials it could read, preserve logs and the package, find affected machines from the inventory, patch and apply settings an upgrade does not turn on, and update vetting rules. Each cites sources, with priority from the written rule, read on 16 Nov 2026.

Facts read on .

What this stage covers

Act when a server is found bad or vulnerable. There are 6 steps here (C-37 to C-42), each a concrete action an engineer can tick.

Sources: AI settings for enterprise, Visual Studio Code docs; Connect Claude Code to tools via MCP, Claude Code docs; Repackaged Amazon SP-API MCP Sends App Secrets to an Undisclosed IP, Knostic.

Steps in order

Do these in order; each step lists how to do it and the register risks it closes.

Sources: AI settings for enterprise, Visual Studio Code docs; Connect Claude Code to tools via MCP, Claude Code docs; Repackaged Amazon SP-API MCP Sends App Secrets to an Undisclosed IP, Knostic; Local Server Security, modelcontextprotocol.io.

Where the settings come from

Setting names appear only where a primary source documents them. Check each against the client version in use before rollout, because the 2026-07-28 MCP revision and client releases changed several defaults.

Sources: AI settings for enterprise, Visual Studio Code docs; Connect Claude Code to tools via MCP, Claude Code docs; Repackaged Amazon SP-API MCP Sends App Secrets to an Undisclosed IP, Knostic; Local Server Security, modelcontextprotocol.io.

Respond: 6 items

C-37: Write a procedure to remove a server everywhere

Define how to take a server out of the managed allow list and remove it from configurations.

Impact: Speed matters once a server is found malicious.

Controls:

  • Remove it from the allowed list first, then from config files and caches.
  • Test the procedure on a harmless server.
  • Register risks: R-07.

Severity: high

Sources: AI settings for enterprise, Visual Studio Code docs (read ); Connect Claude Code to tools via MCP, Claude Code docs (read ).

C-38: Rotate credentials the server could read

List the credentials in the server's environment and files and rotate them.

Impact: Knostic's SP-API finding involves credentials sent to a hardcoded address; rotation limits the damage.

Controls:

  • Rotate tokens, keys and refresh tokens that the server held.
  • Revoke sessions at the authorization server.
  • Register risks: R-36, R-02.

Severity: high

Sources: Repackaged Amazon SP-API MCP Sends App Secrets to an Undisclosed IP, Knostic (read ); Local Server Security, modelcontextprotocol.io (read ).

C-39: Preserve logs and a copy of the package

Keep tool-call logs and the exact package version for analysis.

Impact: Registries remove malicious packages, and evidence goes with them.

Controls:

  • Save the package, its hash and the config that launched it.
  • Export logs for the period the server was active.
  • Register risks: R-40.

Severity: medium

Sources: OWASP MCP Security Cheat Sheet (read ).

C-40: Find affected machines from the inventory

Use the inventory to list every machine and user running the server or the affected version.

Impact: Scope decides how many credentials to rotate.

Controls:

  • Query by package name and version.
  • Include project-scoped configs.
  • Register risks: R-07.

Severity: high

Sources: Evo ADS MCP Governance Goes GA, Snyk (read ); What's new in Microsoft Defender for Endpoint (read ).

C-41: Patch and apply the settings that upgrades do not turn on

Upgrade affected servers and SDKs, then enable settings the fix needs.

Impact: Some advisories say upgrading alone changes nothing.

Controls:

  • Check the advisory text for required settings such as the audience check or expectedIssuer.
  • Re-test after the change.
  • Register risks: R-08, R-11.

Severity: high

Sources: GHSA-w4fh-qvv9-3v23: MCP Python SDK bearer-token audience (read ); GHSA-6qxp-vccf-f47h: MCP TypeScript SDK OAuth client credentials (CVE-2026-104850) (read ).

C-42: Update vetting rules after each incident

Add what you learned to the vetting checks and catalog rules.

Impact: Each incident shows a gap in review.

Controls:

  • Record the cause and the control that would have caught it.
  • Update the checklist edition and note the date.
  • Register risks: R-06.

Severity: medium

Sources: OWASP MCP Security Cheat Sheet (read ).