AI agent governance: content scanning, audit logs, policy evaluation, session management.
Connect Runs on your machine
claude mcp add bulwark -e BULWARK_CONFIG=<BULWARK_CONFIG> -e BULWARK_SESSION_TOKEN=<BULWARK_SESSION_TOKEN> -- docker run -i --rm ghcr.io/bpolania/bulwark:v0.2.0
{
"mcpServers": {
"bulwark": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/bpolania/bulwark:v0.2.0"
],
"env": {
"BULWARK_CONFIG": "<BULWARK_CONFIG>",
"BULWARK_SESSION_TOKEN": "<BULWARK_SESSION_TOKEN>"
}
}
}
}
{
"mcpServers": {
"bulwark": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/bpolania/bulwark:v0.2.0"
],
"env": {
"BULWARK_CONFIG": "<BULWARK_CONFIG>",
"BULWARK_SESSION_TOKEN": "<BULWARK_SESSION_TOKEN>"
}
}
}
}
{
"servers": {
"bulwark": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/bpolania/bulwark:v0.2.0"
],
"env": {
"BULWARK_CONFIG": "<BULWARK_CONFIG>",
"BULWARK_SESSION_TOKEN": "<BULWARK_SESSION_TOKEN>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
BULWARK_CONFIGOptional | Path to bulwark.yaml configuration file |
BULWARK_SESSION_TOKENOptional, secret | Session token for operator authentication (bwk_sess_...) |
Details
| Package | ghcr.io/bpolania/bulwark:v0.2.0 (OCI, stdio) |
| First published | 25 Feb 2026 |
| Last updated | 25 Feb 2026 |
| Registry name | io.github.bpolania/bulwark |
More cloud and devops servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
