Tool Guardian Proxy
Put a safety proxy in front of MCP tool calls so risky agent actions get gated before they hit your repos, APIs, or production.
Overview
Tool-Guardian-Proxy is an MCP server for the Ship phase that proxies and safeguards client tool-call execution so agents cannot blindly invoke dangerous downstream tools.
What is this MCP server?
- Remote MCP server (SSE) at tool-guardian-mcp.vercel.app — no local daemon required
- Acts as a safety execution proxy between the agent client and downstream tools
- Optional premium settlement via payment-signature header (EIP-3009 TransferWithAuthorization)
- server.schema.json v2025-12-11; package version 1.0.0
- MCP integration layer — not a Claude skill; register the remote URL in your agent
- MCP server version 1.0.0
- Single remote SSE endpoint: tool-guardian-mcp.vercel.app/api/mcp
- Optional premium header: payment-signature (EIP-3009 TransferWithAuthorization)
What problem does it solve?
Connecting powerful MCP tools to your agent feels risky when one mis-parsed instruction could delete data, spend money, or exfiltrate secrets without a checkpoint.
Who is it for?
Indie builders running Claude Code or Cursor with multiple write-capable MCP servers who want protocol-level protection on tool execution.
Skip if: Teams that only use read-only tools with no side effects, or anyone who needs fully offline, self-hosted execution with no remote SSE dependency.
What do I get? / Deliverables
After you register the remote MCP endpoint, tool invocations can flow through a dedicated safety proxy so you have a consistent guard layer before actions execute.
- Registered remote Tool-Guardian MCP connection in your agent config
- Tool calls routed through the safety proxy endpoint during agent sessions
Recommended MCP Servers
Journey fit
How it compares
MCP safety proxy at the tool-call boundary, not an in-repo agent skill or static linter.
Common Questions / FAQ
Who is Tool Guardian Proxy for?
It is for solo and indie builders who use MCP-heavy agent workflows and want an execution proxy that reduces risk when tools can mutate state or touch sensitive systems.
When should I use Tool Guardian Proxy?
Use it during Ship and Operate when you are connecting production-adjacent or high-privilege MCP tools and want calls screened before they run.
How do I add Tool Guardian Proxy to my agent?
Add the remote MCP URL https://tool-guardian-mcp.vercel.app/api/mcp as an SSE server in Claude Code, Cursor, or another MCP client; supply the payment-signature header only if you use premium settlement.