Integrations · AI coding agents
The rulebook writes Cursor rules, the gateway holds the MCP allowlist, and every change Cursor produces still meets the same approval rules.
Control levels
1Observe
We watch, record and flag.
MCP traffic through the Aspian gateway, logged per agent key.
2Gate
The tool waits for an approval.
Team rules and an MCP allowlist pinned by version and hash; changes wait for a human approval.
3Hold
Only Aspian holds the credentials.
The agent holds no production credentials.
Set it up
- 1Generate Cursor rules from your rulebook.
- 2Apply them to your Cursor team.
- 3Point MCP at the Aspian gateway.
Limits worth knowing
- A local mode was reported to bypass team allowlists. The server-side gate closes that gap.
More ai coding agents
See what shipped without approval in your last 90 days.
Install the GitHub App and the scan arrives in minutes: every repo scored, every unreviewed merge and unapproved deploy named. Nothing is blocked until you choose.
Ship like a startup. Prove it like a bank.