mcp-server-security

# MCP Server Security

Comprehensive hardening guide for Model Context Protocol (MCP) servers. MCP is the open

standard for connecting AI agents to external tools, data sources, and services. Because

MCP servers execute real actions on real infrastructure, they are a high-value attack

surface. This skill covers every layer of defense you need before exposing an MCP server

to agents in production.

---

2. MCP Threat Model

Before hardening, understand what you are defending against.

| Threat | Vector | Impact |

|-------------------------------|---------------------------------------------------------------|-------------------------------------|

| Unauthorized tool access | Agent calls tools the user should not have access to | Privilege escalation, data breach |

| Prompt injection via resources| Malicious content in MCP resources influences agent behavior | Arbitrary tool execution |

| Data exfiltration via results | Tool results leak sensitive data back to an untrusted agent | Data loss, compliance violation |

| SSRF via MCP tools | Agent tricks a tool into making internal network requests | Internal service compromise |

| Credential theft | API keys or tokens stored insecurely on the MCP server | Full account takeover |

| Denial of service | Agent floods server with tool calls or huge payloads | Service unavailability |

| Man-in-the-middle | Unencrypted transport between agent and MCP server | Eavesdropping, request tampering |

| Supply chain compromise | Malicious MCP server package or plugin | Arbitrary code execution |

---

3. Transport Security

3.1 TLS for Streamable HTTP and SSE Transports

Every MCP server exposed over HTTP must terminate TLS. Never run plain HTTP in

production.

**Nginx reverse proxy with TLS termination for an MCP server:**

# /etc/nginx/sites-enabled/mcp-server.conf
server {
    listen 443 ssl http2;
    server_name mcp.internal.example.com;

    ssl_certificate     /etc/ssl/certs/mcp-server.crt;
    ssl_certificate_key /etc/ssl/private/mcp-server.key;
    ssl_protocols       TLSv1.3;
    ssl_ciphers         TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256;
    ssl_prefer_server_ciphers on;
    ssl_session_timeout 1d;
    ssl_session_tickets off;

    # HSTS header
    add_header Strict-Transport-Security "max-age=63072000; includeSubDomains" always;

    location / {
        proxy_pass http://127.0.0.1:3001;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-Proto $scheme;

        # SSE-specific: disable buffering so events stream immediately
        proxy_buffering off;
        proxy_cache off;
        proxy_read_timeout 86400s;
    }
}

3.2 mTLS Between Agent and Server

For high-security environments, require the agent (client) to present a certificate.

# Add to the server block above
ssl_client_certificate /etc/ssl/certs/agent-ca.crt;
ssl_verify_client on;
ssl_verify_depth 2;

**Generate a client certificate for an agent:**

# Create CA (one-time)
openssl req -x509 -newkey ec -pkeyopt ec_paramgen_curve:P-256 \
  -days 365 -noenc -keyout ca-key.pem -out ca-cert.pem \
  -subj "/CN=MCP Agent CA"

# Create agent client cert signed by the CA
openssl req -newkey ec -pkeyopt ec_paramgen_curve:P-256 \
  -noenc -keyout agent-key.pem -out agent-csr.pem \
  -subj "/CN=agent-orchestrator-01"

openssl x509 -req -in agent-csr.pem -CA ca-cert.pem -CAkey ca-key.pem \
  -CAcreateserial -out agent-cert.pem -days 90

3.3 Securing stdio Transport

For local stdio