Skip to main content
Glama

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: SINT Protocol

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

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.

F
license - not found
Not graded
quality - not tested
C
maintenance

Maintenance

Maintainers
Response time
2wRelease cycle
2Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

  • A
    license
    B
    quality
    C
    maintenance
    Security gateway that wraps any MCP server with per-tool policies, approval gates, and optional Ed25519-signed decision receipts. Shadow mode logs every tool call without blocking; enforce mode applies block, rate-limit, and minimum-tier rules. Receipts are independently verifiable offline with no accounts needed.
    5
    469
    9
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Security-enforcing MCP proxy that sits between an AI agent and any number of downstream MCP servers, intercepting every tool call through a capability-token policy gateway that can allow, deny, or escalate to human approval before the call reaches any real tool. It also exposes built-in operator tools for approval workflows, audit trail queries, token management, voice/HUD output, and hierarchical
    21
    12
    Apache 2.0
  • A
    license
    A
    quality
    A
    maintenance
    Provides advisory AI-governance checks for MCP hosts and coding agents, enabling policy verdicts, PII masking, and audit traces before executing tool calls.
    3
    122
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    A policy-enforcing MCP gateway that intercepts all tool calls to downstream MCP servers, applying allow/deny/ask rules with human approval and audit logging for safe access to dangerous tools.
    23
    MIT

View all related MCP servers

Related MCP Connectors

  • Security firewall for AI agents — scans MCP calls for injection, secrets, and risks.

  • See, price, and control every tool call your AI agents make: policy checks, cost, and audit tools.

  • Runtime permission, approval, and audit layer for AI agent tool execution.

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/impact-boundary-labs/MCPBoundary'

If you have feedback or need assistance with the MCP directory API, please join our Discord server