Exports telemetry data to OpenTelemetry collectors as a non-authoritative mirror, while JSONL remains the system of record.
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.
contextboundary-gw is a self-hosted MCP gateway that applies deterministic, compiled policy to tool discovery, invocation, and outbound data flow. No model is in the runtime enforcement path.
AARM-aligned strict-determinism profile. All Core requirements (R1–R6) are implemented and CI-verified. Independent conformance review has not been undertaken.
R7 is a designed deterministic divergence: envelope-drift counting replaces semantic-distance tracking to keep a model out of the enforcement path. R8 OpenTelemetry export is implemented as a non-authoritative mirror; JSONL remains the system of record.
The test suite runs locally. It does not require a deployed Worker or any network access after git clone and npm ci.
git clone https://github.com/kannanokannan/contextboundary-gw.git
cd contextboundary-gw
npm ci
export TEST_AUDIT_SEAL_KEY='local-test-value'
export TEST_INTENT_ENVELOPE_BOOTSTRAP_KEY='local-owner-bootstrap-value'
npm run test:conformance
npm run test:interception
npm run test:receipts
npm run test:intent-envelope
npm run test:r4
npm run test:r6
npm run test:r8
npm run test:server-discovergit clone https://github.com/kannanokannan/contextboundary-gw.git
Set-Location contextboundary-gw
npm ci
$env:TEST_AUDIT_SEAL_KEY = 'local-test-value'
$env:TEST_INTENT_ENVELOPE_BOOTSTRAP_KEY = 'local-owner-bootstrap-value'
npm run test:conformance
npm run test:interception
npm run test:receipts
npm run test:intent-envelope
npm run test:r4
npm run test:r6
npm run test:r8
npm run test:server-discoverTEST_AUDIT_SEAL_KEY and TEST_INTENT_ENVELOPE_BOOTSTRAP_KEY are arbitrary, non-empty values used only by local tests; they are not production secrets. test:conformance and test:intent-envelope require both values. test:interception requires TEST_AUDIT_SEAL_KEY. The other four existing suites create their own ephemeral test material; test:server-discover needs no test values.
Suite | Coverage | Local execution |
| 21 normative policy scenarios | Local Worker |
| 9 assertions for discovery and invocation interception | Local Worker and local spy upstream |
| 10 assertions for chained receipts and public-key verification | Node-only |
| 28 assertions for frozen declared-intent envelopes | Local Worker |
| 14 assertions for MODIFY and DEFER outcomes | Local Worker and local spy upstream |
| 17 assertions for agent signatures, rotation, replay, and public-key verification | Local Worker |
| 10 assertions for OpenTelemetry export | Node-only with a local collector |
| 15 assertions for locally-answered, policy-filtered discovery | Local Worker and local spy upstream |
Related MCP server: protect-mcp
tools/call is evaluated before forwarding; only an allow decision is proxied upstream.
tools/list is evaluated; a non-ALLOW result returns an empty list, and an allowed upstream list is filtered to permitted capabilities and envelope scope.
All other MCP methods are proxied to UPSTREAM_MCP_URL, with boundary-* identity and signature headers stripped before forwarding.
The gateway also handles boundary/evaluate, boundary/session.start, and boundary/deferred.resume locally.
Decision receipts are hash-chained and sealed with Ed25519. Verification uses public keys only, so a third party can verify a receipt without a private key. HMAC-SHA256 is used only for the intent-envelope bootstrap proof, not for the gateway receipt seal.
Run the verifier with a receipt and public-key bundle:
node audit/verify-receipt.mjs receipt.json --public-keys public-keys.jsonSee audit/verify-receipt.mjs and the runnable AMS ticket-change example.
This is a self-hosted reference implementation, not a hosted service; it is not deployed.
Independent conformance review has not been undertaken.
The gateway governs what passes through it. Agents that do not speak MCP, direct API calls that bypass the gateway, and side channels are outside its control. It is a control point, not a network perimeter.
Determinism is a runtime property. Policy authoring, capability registration, and intent-envelope issuance sit upstream of the enforcement path, not inside it.
Adversarial scenarios are authored in this repository. No external red team has reviewed them.
R6 proves that the key registered to agent X signed an action. It does not identify the human behind that agent.
R7 deliberately differs from AARM's semantic-distance approach by using deterministic envelope-drift counting.
Production operation requires deployment-specific Worker bindings, an agent public-key registry, and gateway signing material configured outside this repository.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
MCP gateway with runtime security policy, tool-call-level control, and audit of agent actions.
MCP gateway: one connection for your AI apps, with tool policies, PII redaction and audit logs.
Find, vet, and run MCP tools through a secure audited gateway with prompt-injection risk scoring
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
