Define repository-wide MCP installation safety guidance

[coderabbitai]

Summary

Define repository-wide MCP installation safety guidance for ECC setup guides.

Rationale

MCP server configuration can execute third-party code and expose tool access. The guidance must apply consistently across all documentation that instructs users to install or configure MCP servers. This work is separate from the narrow documentation fix in PR #2958.

Required changes

Create and review a common policy for MCP installation guidance. The policy should require:

• An official vendor or source link.
• Verification of publisher identity.
• An exact version and integrity pin where the installation method supports it.
• Review and explicit allowlisting of MCP tools before configuration.
• Least-privilege permissions or isolation where feasible.
• Dated, evidence-based wording for package publication and ownership status.

Apply the approved guidance consistently to setup guides and other documentation that reference MCP server installation or configuration.

Affected areas

• skills/**/*.md
• commands/**/*.md
• agents/**/*.md
• Any other ECC documentation that configures MCP servers or uses npx to install MCP packages.

Acceptance criteria

• A reviewed repository-wide MCP installation safety policy exists.
• The policy defines provenance, publisher verification, version/integrity pinning, tool allowlisting, and least-privilege or isolation requirements.
• Applicable setup guides use consistent guidance or link to the common policy.
• Documentation avoids unsupported absolute claims about package publication or npm scope ownership.
• The work receives a dedicated design review before broad documentation updates.

Backlinks

• PR: docs(autonomous-agent-harness): remove unpublished @anthropic/* MCP package references #2958
• Review comment: docs(autonomous-agent-harness): remove unpublished @anthropic/* MCP package references #2958 (comment)
• Requested by: @kavish-19