Back to product

SECURITY MODEL

SANDBOXED

Boundaries you can
reason about.

CodeMCP is a local bridge. Its security model is built around project boundaries, protected paths, explicit permissions, and visible file changes.

01020304

Project boundary

Paths are resolved and constrained to the configured project. Attempts to traverse outside that project are rejected by the path guard.

configured project → allowed path

Protected paths

Sensitive paths, including credential locations and environment variables (.env*), are protected from tool access automatically.

protected path → denied

Permission modes

Filesystem changes are controlled by permission mode. In approval mode, a proposed change must be explicitly accepted in the terminal before it touches disk.

write request → approval → filesystem

Encrypted credentials

CodeMCP implements encrypted credential storage for credentials it manages. No unencrypted secrets are persisted or leaked to remote logs.

credential → encrypted storage