MCP config security rules
Every check of the free MCP config audit: written-in secrets, unpinned servers, plain-HTTP remotes, broad filesystem access, with why each matters and the fix.
- High
Secret written in the config
A value in env, headers, args or the URL looks like an API key or token. Config files get committed, synced, pasted into chats and read by every tool on the machine; a key written in them is as exposed as the file.
- High
Remote server over plain HTTP
The connection to the server is not encrypted: anyone on the network path can read the tool calls, the data they return and any token sent with them, or change them.
- High
Filesystem server can read your whole disk or home folder
The filesystem server can read and write everything under the folders it is given. Giving it /, ~ or a whole drive exposes SSH keys, browser profiles, other projects and cloud credentials to every prompt.
- Medium
npx runs whatever version is latest
Without an exact version, npx downloads the newest release each time the client starts. A compromised or broken release reaches you without any review, with the access you gave the server.
- Medium
uvx or pipx runs whatever version is latest
Without a pinned version, uvx and pipx run the newest release from PyPI at each start, so a malicious or broken release runs with no review.
- Medium
Docker image without a fixed version
An image without a tag, or with :latest, can change under you: the next pull runs different code.
- Medium
Server started through a shell command
bash -c, sh -c, cmd /c or powershell -Command hide what actually runs inside a string: it is hard to review, and easy to change unnoticed.
- Low
A whole environment file is passed to the server
Loading a whole .env file gives the server every secret in it, not just the one it needs.
- Low
The same server is configured twice
Two entries run the same package under different names: twice the tools in every conversation, and two places to keep up to date.
- Info
Remote server on a host we don't know
A remote MCP server sees every tool call made to it. Check who runs it, what it logs and its terms before sending it your data.
- Info
Package not in our list of known MCP servers
Most MCP servers are small community packages. Look-alike names and typos are a known way to get malicious code installed.
- Info
Many servers configured
More than 15 servers add their tools to every conversation, use up context and widen what a prompt injection can reach.