Audit MCP (Model Context Protocol) server configurations for security issues. Use this skill when: - Reviewing .mcp.json files for security risks - Checking MCP server args for hardcoded secrets or shell injection patterns - Validating that MCP servers use pinned versions (not @latest) - Detecting u

MCP Security Audit Audit MCP server configurations for security issues — secrets exposure, shell injection, unpinned dependencies, and unapproved servers. Overview MCP servers give agents direct tool access to external systems. A misconfigured .mcp.json can expose credentials, allow shell injection, or connect to untrusted servers. This skill catches those issues before they reach production. When to Use Reviewing any .mcp.json file in a project Onboarding a new MCP server to a project Auditing all MCP servers in a monorepo or plugin marketplace Pre commit checks for MCP configuration changes Security review of agent tool configurations Audit Check 1: Hardcoded Secrets Scan MCP server args and env values for hardcoded credentials. Good practice — use env var references: Bad — hardcoded credentials: Audit Check 2: Shell Injection Patterns Detect dangerous command patterns in MCP server args. Audit Check 3: Unpinned Dependencies Flag MCP servers using @latest in their package references. Good — pinned version: Bad — unpinned: Audit Check 4: Full Audit Runner Combine all checks into a single audit. Usage: Output Format Related Resources [MCP Specification](https://modelcontextprotocol.io/) [Agent Governance Toolkit](https://github.com/microsoft/agent governance toolkit) — Full governance framework with MCP trust proxy [OWASP ASI 02: Insecure Tool Use](https://owasp.org/www project agentic ai threats/)

mcp-security-audit