メニュー
Harden locally deployed MCP servers against network exposure and host compromise. Use when building, deploying, or reviewing MCP servers that run on a user's local machine.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Security-focused review of AI-generated or AI-assisted code. Use when reviewing code produced by AI coding assistants, auditing AI-generated patches, verifying AI-assisted contributions before merge, or when a review needs to account for failure modes specific to AI code generation.
Configure Kubernetes network security including host access restrictions, network policies, port management, and connectivity requirements. Use when writing, reviewing, or auditing pod specs, Services, NetworkPolicies, or NetworkAttachmentDefinitions.
Secure AI-powered products and infrastructure. Use when integrating LLM APIs, deploying model-serving infrastructure, building agent workflows, connecting MCP servers, or reviewing AI system architecture for security gaps.
Enforce standard authentication for external data source connections. Use when integrating, configuring, or reviewing connections from AI systems to external databases, APIs, or data services.
Harden container images and runtime configuration. Use when building, reviewing, or auditing Containerfiles, Dockerfiles, container compose files, or Kubernetes pod security settings.
Supply chain security audit using CLI vulnerability scanners, license compliance checks, and supply chain risk assessment. Use when auditing project dependencies for known CVEs, license concerns, and supply chain health.
| name | hardening-local |
| description | Harden locally deployed MCP servers against network exposure and host compromise. Use when building, deploying, or reviewing MCP servers that run on a user's local machine. |
| category | secure_development |
| subcategory | mcp-server |
MCP servers running locally on a user's machine require specific hardening to prevent network exposure and protect the host.
Bind to the loopback interface only:
# CORRECT - bind to loopback only
host: 127.0.0.1
port: 8080
# WRONG - exposed to the entire network
host: 0.0.0.0
port: 8080
Binding to 0.0.0.0 exposes the MCP server to the local network and potentially the internet, allowing unauthorized access.
| Control | Details |
|---|---|
| Dedicated user | Run as a dedicated low-privilege OS user, not the user's main account |
| No root | Never run as root |
| Minimal permissions | Grant only the filesystem and network permissions needed |
| Filesystem isolation | Use containers or chroot to limit host filesystem access |
| Control | Details |
|---|---|
| Containers | Run in a container (Podman, Docker) to isolate from the host |
| chroot | Use chroot jail to limit filesystem visibility |
| Read-only access | Mount host directories as read-only unless the server requires write access |
| No home directory access | Do not grant access to the user's entire home directory |
127.0.0.1 only, never 0.0.0.0