Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Runestone-Labs/gatekeeperWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/runestone-labs/gatekeeper/mcp-server-gatekeeper)<a href="https://agentmods.dev/mcp/runestone-labs/gatekeeper/mcp-server-gatekeeper"><img src="https://agentmods.dev/badge/mcp/runestone-labs/gatekeeper/mcp-server-gatekeeper/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/runestone-labs/gatekeeper/mcp-server-gatekeeper"><img src="https://agentmods.dev/badge/mcp/runestone-labs/gatekeeper/mcp-server-gatekeeper.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
gatekeeper scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"gatekeeper": {
"command": "npx",
"args": [
"-y",
"@runestone-labs/gatekeeper-mcp"
],
"env": {
"GATEKEEPER_ROLE": "",
"GATEKEEPER_URL": "",
"GATEKEEPER_AGENT_NAME": "",
"GATEKEEPER_RUN_ID": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 15 lines scan A bdcca970553d
gatekeeper is an MCP server published in the GitHub repository Runestone-Labs/gatekeeper (0 stars, last pushed 15d ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
koma-gate-mcp
Classifies prompt injection, jailbreaks, and out-of-scope user input before agents act on it. Runs locally from the koma-gate-mcp npm package. Needs 6 environment variables to run.
koma-core-mcp
Protected RAG storage — agents discover public metadata, content only by access token. Runs locally from the koma-core-mcp npm package. Needs 1 environment variable to run.
agentguards
MCP server "agentguards", hosted remotely at prod.agentguards.co, as configured in alelaguard/agentguards-plugins.
promptrejectormcp
Security gateway for AI agents: detects prompt injections, jailbreaks, and common vulnerabilities. Runs locally from the prompt-rejector npm package. Needs 1 environment variable to run.
promptwall
LLM prompt injection firewall with session tracking, explainability and multilingual detection. Runs locally from the promptwall Python package.
mcp-governance-proxy
MCP server "mcp-governance-proxy" as configured in andreas-altamirano/mcp-governance-proxy. Runs locally from the mcp-governance-proxy Python package.