Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Action-level governance for AI agents -- control what they DO, not what they SAY
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"agent-guardrail": {
"command": "uvx",
"args": [
"agent-guardrail"
]
}
}
}在终端中运行这条命令
claude mcp add agent-guardrail -- uvx agent-guardrail粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"agent-guardrail": {
"command": "uvx",
"args": [
"agent-guardrail"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"agent-guardrail": {
"type": "stdio",
"command": "uvx",
"args": [
"agent-guardrail"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
发布者(JarvisOnM4)不是仓库所有者(eren-solutions);可能是其他人代为上架的
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 0 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.2)于8个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:Spec Driven Development, Remote Desktop Commander, NexusWindows
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Windows computer use in the background: desktop apps driven without your mouse or keyboard.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Action-level governance for AI agents — control what they DO, not what they SAY.
AI agents are getting tool access. They can run shell commands, make API calls, read files, spend money. But most "guardrails" only filter what agents *say* — not what they *do*.
Real incidents:
You need action-level control. Not output filtering.
Agent Framework --> Agent Guardrail --> {allow, deny, require_approval}
--> Flight Recorder logs everything
Zero dependencies. Python stdlib only. SQLite for storage.
pip install agent-guardrail
agent-guardrail register "my-research-agent" --framework langchain
agent-guardrail apply-template moderate
agent-guardrail eval bash --target /workspace/test.sh # -> allow agent-guardrail eval bash --target /etc/shadow # -> deny agent-guardrail eval sudo # -> deny
from agent_guardrail import GuardrailStore, PolicyEngine, DEFAULT_POLICIES
store = GuardrailStore() # ~/.agent-guardrail/guardrail.db engine = PolicyEngine(store)
agent = store.register_agent("my-agent", framework="langchain")
store.save_policy({ "name": "moderate", "agent_id": agent["id"], "rules": DEFAULT_POLICIES"moderate", })
decision = engine.evaluate(agent["id"], "bash", target="/workspace/run.sh")
decision = engine.evaluate(agent["id"], "bash", target="/etc/shadow")
decision = engine.evaluate_and_record( agent_id=agent["id"], action_type="api_call", tool_name="openai_chat", cost_usd=0.05, session_id="session-123", )
from agent_guardrail import GuardrailStore, PolicyEngine
class GuardrailCallback: """Drop into any LangChain agent as a callback handler.""" def init(self, agent_id, db_path=None): self._engine = PolicyEngine(GuardrailStore(db_path=db_path)) self.agent_id = agent_id
def on_tool_start(self, serialized, input_str, **kwargs): decision = self._engine.evaluate_and_record( agent_id=self.agent_id, action_type="tool_call", tool_name=serialized.get("name"), target=input_str[:200], ) if decision.decision == "deny": raise PermissionError(f"Guardrail: {decision.reason}")
from agent_guardrail import GuardrailStore, PolicyEngine
def make_guardrail(agent_id, db_path=None): engine = PolicyEngine(GuardrailStore(db_path=db_path))
def check(task_output): decision = engine.evaluate_and_record( agent_id=agent_id, action_type="task_output", target=str(task_output)[:200], ) if decision.decision == "deny": return (False, f"Blocked: {decision.reason}") return (True, task_output) return check
from agent_guardrail import GuardrailStore, PolicyEngine
import functools
def guardrail(agent_id, action_type="function_call", db_path=None): engine = PolicyEngine(GuardrailStore(db_path=db_path)) def decorator(func): @functools.wraps(func) def wrapper(*args, **kwargs): target = str(args[0])[:200] if args else None decision = engine.evaluate_and_record( agent_id=agent_id, action_type=action_type, tool_name=func.name, target=target, ) if decision.decision == "deny": raise PermissionError(f"Guardrail: {decision.reason}") return func(*args, **kwargs) return wrapper return decorator
@guardrail("my-agent", action_type="bash") def run_command(cmd): ...
The library is for humans. The API is for agents.
An orchestrator running 5 sub-agents doesn't pip install — it calls an endpoint.
# Start the proxy server
pip install agent-guardrail[proxy] guardrail-proxy --port 8300 --admin-key YOUR_ADMIN_KEY
# Register an agent (admin)
curl -X POST http://localhost:8300/v1/agents \ -H "X-Admin-Key: YOUR_ADMIN_KEY" \ -d '{"name": "research-agent", "framework": "crewai"}'
curl -X POST http://localhost:8300/v1/evaluate \ -H "X-API-Key: gw_agent_key_here" \ -d '{ "agent_id": "...", "action_type": "bash", "tool_name": "shell", "target": "/etc/shadow", "cost_usd": 0.0 }'
Full API docs at http://localhost:8300/docs (Swagger UI).
Free tier included. Pay with Bitcoin when you need more.
| Tier | Evaluations | Price | Per Eval |
|---|---|---|---|
| Free | 100/day per agent | $0 | $0 |
| Starter | 1,000 | $10 | $0.010 |
| Growth | 5,000 | $40 | $0.008 |
| Scale | 25,000 | $150 | $0.006 |
Credits are prepaid and never expire. Admin-authenticated requests bypass billing entirely.
How it works:
# Check your balance
curl http://localhost:8300/v1/billing/balance \ -H "X-API-Key: gw_your_agent_key"
curl -X POST http://localhost:8300/v1/billing/checkout \ -H "X-API-Key: gw_your_agent_key" \ -d '{"pack_id": "pack_1000"}'
When free tier is exhausted and no credits remain, /v1/evaluate returns 402 Payment Required with a link to available packs.
Self-hosted billing: Set BLOCKONOMICS_API_KEY and BLOCKONOMICS_WEBHOOK_SECRET environment variables. Without these, billing is disabled and all evaluations proceed without metering (backward compatible).
{
"tool_allowlist": ["read_file", "write_file"], # Only these tools allowed "tool_denylist": ["sudo", "rm", "delete*"], # These tools always denied "target_allowlist": ["/workspace/*"], # Only these targets allowed "target_denylist": ["/etc/*", "*.env", "*.key"], # These targets always denied "network_allowlist": ["api.openai.com"], # Allowed network targets "network_denylist": ["*"], # Denied network targets "spend_cap_daily_usd": 25.0, # Daily spend limit "spend_cap_total_usd": 500.0, # Lifetime spend limit "require_approval": ["bash", "install"], # Human approval required "risk_threshold": 0.8, # Auto-approval gate }
Patterns support glob matching (*, ?, [abc]).
Kill switch? ──deny──> DENY
| Agent enabled? ──no──> DENY | Spend cap? ──exceeded──> DENY | Tool denylist? ──match──> DENY | Target denylist? ──match──> DENY | Approval required? ──match──> REQUIRE_APPROVAL | Risk threshold? ──exceeded──> REQUIRE_APPROVAL | Tool allowlist? ──not in list──> DENY | Target allowlist? ──not in list──> DENY | DEFAULT ──> ALLOW
+-------------------+ +------------------+ +-----------------+
| Agent Framework |---->| Billing Check |---->| Policy Engine | | (LangChain, | | (free tier / | | (evaluate) | | CrewAI, custom) | | credits) | +-----------------+ +-------------------+ +------------------+ | | v | +------------------------+ 402 if empty | Decision: | | allow / deny / | | require_approval | +------------------------+ | v +-----------------+ | Flight Recorder| | (SQLite) | +-----------------+
+-------------------+ +------------------+ | BTC Payment |---->| Blockonomics | | (checkout) | | (xpub-derived | +-------------------+ | addresses) | +------------------+ | webhook (status=2) | v +------------------+ | Credit Grant | | (billing_ledger)| +------------------+
| Feature | Agent Guardrail | Guardrails AI | NeMo Guardrails | DIY |
|---|---|---|---|---|
| Action-level control | Yes | No (output only) | No (dialogue only) | Manual |
| Spend caps | Yes | No | No | Manual |
| Kill switch | Yes | No | No | Manual |
| Flight recorder | Yes | No | No | Manual |
| Pay-per-eval billing | Yes (BTC) | No | No | Manual |
| Zero dependencies | Yes | No (many) | No (many) | Varies |
| Framework agnostic | Yes | LangChain-focused | LangChain-focused | Yes |
| Hosted API | Yes | Cloud only | No | Manual |
agent-guardrail agents # List registered agents
agent-guardrail register "name" # Register a new agent agent-guardrail kill # Emergency kill switch agent-guardrail unkill # Revoke kill switch agent-guardrail policies # List policies agent-guardrail apply-template agent-guardrail actions [--agent X] [--decision deny] agent-guardrail replay # Session replay agent-guardrail approvals # Pending approvals agent-guardrail approve # Approve action agent-guardrail deny # Deny action agent-guardrail eval [--target X] [--cost 0.5] agent-guardrail stats # Statistic
只显示了开头部分;其余内容请在仓库中阅读