Install locally. Enforce globally.
Run greene serve, configure policies in the dashboard, point Cursor at localhost:8080/mcp, and every packet passes through JWT auth, OPA guard, MCP federation, context lock, x402 escrow, PAIQ, and DeltaState sandbox.
Four steps, start to audit.
Define a guard rail
Create a guard rail (a budgeted policy context) and set its limits — daily cap, per-transaction max, monthly cap, blocked categories, and the threshold above which a human must approve.
Connect your agent
Add Greene Comply to Cursor or Claude Desktop with the native MCP server, or mint a gc_ API key and call the REST endpoint from your own stack.
Every spend is evaluated
Before any money moves, the request runs through the policy engine. The result is approve, deny, or hold-for-approval — returned in milliseconds with a clear reason.
Logged & reconciled
Approvals, denials, and overrides are written to an immutable audit log, and the cost lands in your unified ledger — export-ready for finance and auditors.
What gets checked on every request.
- ✓Daily limit and monthly cap for the guard rail
- ✓Per-transaction maximum
- ✓Blocked merchant categories
- ✓Approval threshold — spends above it are held for a human
- ✓Account freeze (kill switch) and remaining credits
Pass any single check and a spend can still be held; fail any one and it is denied with a machine-readable code your agent can act on.