Gatekeeper runs on your own machine — the client starts it, so there is no endpoint to ping. 49 installs a week from npm. Last commit 9 Oct 2026.
Run MCP tool calls through Runestone Gatekeeper — policy enforcement, human approval, audit.
What the code does
We read the source, 7 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
spawn(command, args, { detached: true, stdio: 'ignore' }).unref();
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add gatekeeper -e 'GATEKEEPER_ROLE=<GATEKEEPER_ROLE>' -- npx -y @runestone-labs/gatekeeper-mcp{
"mcpServers": {
"gatekeeper": {
"command": "npx",
"args": [
"-y",
"@runestone-labs/gatekeeper-mcp"
],
"env": {
"GATEKEEPER_ROLE": "<GATEKEEPER_ROLE>"
}
}
}
}[mcp_servers.gatekeeper]
command = "npx"
args = ["-y", "@runestone-labs/gatekeeper-mcp"]
env = { GATEKEEPER_ROLE = "<GATEKEEPER_ROLE>" }{
"mcpServers": {
"gatekeeper": {
"command": "npx",
"args": [
"-y",
"@runestone-labs/gatekeeper-mcp"
],
"env": {
"GATEKEEPER_ROLE": "<GATEKEEPER_ROLE>"
}
}
}
}{
"servers": {
"gatekeeper": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@runestone-labs/gatekeeper-mcp"
],
"env": {
"GATEKEEPER_ROLE": "<GATEKEEPER_ROLE>"
}
}
}
}Put your own value in place of
<GATEKEEPER_ROLE> (Policy role this server presents to Gatekeeper for every call. Required).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
GATEKEEPER_URL (Base URL of the Gatekeeper server. Default http://127.0.0.1:3847), GATEKEEPER_AGENT_NAME (Agent name recorded in Gatekeeper audit logs. Default mcp-client), GATEKEEPER_RUN_ID (Optional run-correlation id so calls count toward one per-run budget).
Alternatives to Gatekeeper
same job, measured the same wayCordon for MCP. Security gateway with policy enforcement, audit log, and HITL approvals.
Deterministic policy enforcement and MCP management for AI agent tool calls.
Policy-based governance for AI agent tool calls. YAML policy, approval gates, audit logging.
Governance proxy for MCP servers — policy evaluation, human approval, audit trails.
Add human approval to AI agent workflows through cQnce authorization tools.
Pre-execution gate for AI-agent tool calls. Touch ID approval. Tamper-evident audit log.
Policy enforcement plane for MCP: every tool call ends in a verdict. Self-hosted, MIT.
Zero-trust MCP security proxy with policy enforcement, PII scrubbing, approvals, and audit trails.
Gatekeeper — questions
Answers built from our own checks of this server.