Local MCP Server Security: What to Check Before You Install

By Numan ·

A practical checklist for reviewing local MCP servers, permissions, package provenance and updates.

Local MCP Server Security: What to Check Before You Install

A local MCP server runs on your machine and may inherit access to files, environment variables, and network services. The MCP project's local-server security guide (https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/docs/docs/2026-07-28/tutorials/security/local-server-security.mdx) recommends checking provenance, pinning versions, and limiting the runtime's access.

Before installing

Read the server's source or trusted release notes, check who maintains it, and identify which tool calls it exposes. A listing in a catalog is a discovery aid, not proof that the package is safe. Record why you need the server and what the agent can do through it.

Pin a version for repeatable installation, then update deliberately when a security advisory applies. The official guide notes that pinning only a top-level package may still allow dependencies to change; a container image pinned by digest freezes a wider dependency tree. Choose the level of reproducibility appropriate to the risk.

At runtime

Give the server only the directories and environment variables it needs. Avoid passing a broad cloud credential to a tool that only lists public issues. Where practical, run it in a container or restricted process with network and filesystem limits. Keep write-capable tools separate from read-only tools.

When it returns data

Treat tool output as untrusted input to the agent, especially when it includes web pages, repository text, or messages. Test one sample that contains instructions aimed at the agent. The content should be treated as data, not as a new permission grant.

Finally, record who approved installation, the pinned version, and the update plan. Revisit the permission list when the server gains a new tool. Our agent security checklist (https://ubits.tech/learning/p/ai-agent-security-checklist-prompt-injection-tool-access) gives a wider review path.