{"slug": "8-safe-by-default-mcp-servers-for-infra-and-the-governance-model-behind-them", "title": "8 safe-by-default MCP servers for infra — and the governance model behind them", "summary": "A developer has released a family of safe-by-default Model Context Protocol (MCP) servers for infrastructure management, designed to give AI agents graduated access to production systems. The servers implement a layered policy engine with read-only, read-write, and admin modes, plus typed confirmations for destructive operations, and are available as MIT-licensed TypeScript packages on npm.", "body_md": "Giving an AI agent access to production infrastructure is a great way to move fast — and a great way to have it drop a database because a prompt was ambiguous. I wanted the upside without the footguns, so I built a family of [Model Context Protocol](https://modelcontextprotocol.io) servers that share one safe-by-default governance model.\n\nMCP lets an agent call tools. For infra, those tools can be `delete_topic`\n\n, `DROP TABLE`\n\n, `delete_resource_group`\n\n. The usual answer is \"just don't expose the dangerous ones\" — but then the server isn't useful when you *do* need them. I wanted graduated, explicit control instead.\n\nEvery server shares the same layered policy engine:\n\n`read-only`\n\n→ `read-write`\n\n→ `admin`\n\n. Tools above the current mode are `system`\n\nDB, internal Kafka topics, the master realm) are readable but never mutable.`ALLOW_DELETE`\n\nflag on top of admin mode.`confirm`\n\nvalue that echoes the exact target name. A boolean isn't enough.All MIT-licensed, TypeScript, published on npm as `@dockndevai/mcp-*`\n\n:\n\n```\nnpx -y @dockndevai/mcp-kubernetes\n```\n\nOr in Claude Code:\n\n```\nclaude mcp add kubernetes -e KUBECONFIG_PATH=~/.kube/config -e K8S_MODE=read-only -- npx -y @dockndevai/mcp-kubernetes\n```\n\nEvery repo has per-client setup for Claude, Cursor, Codex, VS Code, and Windsurf.\n\nRepos: [https://github.com/dockndevai](https://github.com/dockndevai)\n\nI'd love feedback — especially on whether the mode + typed-confirmation split is the right default for infrastructure MCP servers.", "url": "https://wpnews.pro/news/8-safe-by-default-mcp-servers-for-infra-and-the-governance-model-behind-them", "canonical_source": "https://dev.to/dockndevai/8-safe-by-default-mcp-servers-formcp-ai-devops-opensource-infra-and-the-governance-model-4gi8", "published_at": "2026-08-23 16:26:47+00:00", "updated_at": "2026-08-23 16:44:06.822755+00:00", "lang": "en", "topics": ["ai-agents", "ai-infrastructure", "developer-tools"], "entities": ["Model Context Protocol", "dockndevai", "Claude", "Cursor", "Codex", "VS Code", "Windsurf", "npm"], "alternates": {"html": "https://wpnews.pro/news/8-safe-by-default-mcp-servers-for-infra-and-the-governance-model-behind-them", "markdown": "https://wpnews.pro/news/8-safe-by-default-mcp-servers-for-infra-and-the-governance-model-behind-them.md", "text": "https://wpnews.pro/news/8-safe-by-default-mcp-servers-for-infra-and-the-governance-model-behind-them.txt", "jsonld": "https://wpnews.pro/news/8-safe-by-default-mcp-servers-for-infra-and-the-governance-model-behind-them.jsonld"}}