mcp-boundary
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
MCP Boundary
A local proxy that wraps your MCP servers and checks each tool call against your policy and the current state before any server tool is called. When it blocks, the agent gets back a reason it can act on.
Website: https://mcpboundary.com · Docs: https://mcpboundary.com/docs/mcp-boundary
What it does
Wrap an existing local MCP server — your agent keeps the same tools, every call passes the boundary first.
Choose which tools the agent sees — expose, hide, or keep dashboard-only.
Allow, block, or hold for review — with a structured reason the agent can act on.
Restrict specific arguments, not whole tools — e.g. allow only certain recipients or IDs.
Limit response sizes and timeouts — and throttle repeated calls to contain runaway loops.
Bind writes to observed state — don't run a write if the world changed since the read.
Inspect every call, decision, reason, and outcome in a local dashboard.
Related MCP server: agent-firewall
How it works
MCP Boundary sits between your MCP client and your local MCP servers. Your agent connects to MCP Boundary as a server entry; MCP Boundary checks each tool call against your policy and the current state, then forwards only admitted calls to the real server. When it blocks, the agent gets back a reason it can act on — re-check state, narrow scope, or stop retrying.
Download
Windows and Linux builds with SHA-256 checksums (current release v0.2.3): → https://mcpboundary.com
Quick start from an extracted package — Windows: .\mcpboundary.exe quickstart email · Linux: ./mcpboundary quickstart email
Docs
Getting started, policy examples, tested servers — https://mcpboundary.com/docs/mcp-boundary
How it works — https://mcpboundary.com/how-it-works
MCP Tool Rules (writing policies) — https://mcpboundary.com/mcp-tool-rules
Scope
MCP Boundary works best with local command-based stdio MCP servers. Only calls routed through MCP Boundary are covered. It is not an enterprise security gateway, a DLP system, a prompt-injection detector, or a replacement for code review, database permissions, or email approval processes.
License
MCP Boundary is free to download and use, distributed under its own license and terms — see LICENSE.md and TERMS.md in the release package. All rights reserved.
Built by Impact Boundary Labs.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
MCP enforcement layer that intercepts AI agent actions and blocks rule violations before execution.
Zero-secret MCP gateway for AI agents: risk-scored, audited calls with human-in-the-loop approval.
Security & DLP proxy for MCP: tool-poisoning scans, PII redaction on tool args/results. Beta.
Related MCP Servers
- AlicenseAqualityBmaintenanceAn MCP proxy that enforces policy on every tool call, blocking or flagging actions before they reach downstream MCP servers.162 npmMIT
- AlicenseNot gradedqualityBmaintenanceSits in front of any MCP server to enforce allow/ask/block policies on tool calls, paths, shell commands, and network domains, with local approval prompts and an audit log.MIT
- AlicenseNot gradedqualityBmaintenanceProvides a governance layer for MCP servers, enforcing policy-based allow/deny/approval rules, requiring human approval for risky calls, and recording an auditable trail of every AI agent tool call.MIT
- AlicenseNot gradedqualityBmaintenanceEnforces allow/deny/ask policies on MCP tool calls before they reach downstream servers, with tamper-evident audit logging.MIT