Boundary Guard x402
io.github.LarryLemonBot/boundary-guard-x402
MCP tools for x402 readiness, paid-path probes, launch packs, and trust receipts.
Install surfaces
How Boundary Guard x402 runs, per the official MCP registry entry.
- streamable-http
https://x402-resource-scanner.vercel.app/mcp
Governed execution
How KLA gates calls to Boundary Guard x402 once it is connected.
A published policy defines which Boundary Guard x402 actions an agent may take and under what conditions. Each call passes through a policy gate at the tool-call boundary. Permitted actions execute, with the policy basis recorded. Flagged actions execute and are sampled for scheduled human review. High-stakes actions pause and route to a named reviewer on the Decision Desk. The call, the policy decision, and any approval are sealed as an evidence record.
KLA also governs the agent frameworks and model providers you already run. See integrations.