MCP security basics: lock permissions first

MCP can read files and run commands. Default trust hands over repo keys.

Install only servers whose job you can explain. A listing here is public metadata, not an audit.

Narrow working directories and allowed paths. Put secrets in environment variables, not in a committed mcp.json.

Prove the connection with a read-only action before enabling writes or execution. Database and cloud servers need least-privilege accounts.

Review the connected list and remove unused servers. “Connected” does not mean the process is harmless.