coulomb/qonto-assistant
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
A policy governed qonto domain API and MCP assistant for binky-control.
31 commits 1 branch 0 tags 488 KiB
Find a file
tegwick 3faf1fed71 Add SecurityPractice.md, Security Genome record, and deny-escalation lockout 
Design doc for hardening qonto-assistant before deployment to
railiance01: this is the first fleet service that must be
internet-reachable (external harness clients, not just in-cluster
jobs) while holding a real bank credential. Covers identity (key-cape
in place of the interim bearer token), authorization (finance.qonto.read
in flex-auth + tenant-engine capability roles instead of the
hardcoded default_tenant_id), network exposure (facade-only internet
address), isolation profile, and a Kings Guard mapping (the existing
audit stream is already Immune-Observation-shaped; nothing to rebuild
later).

Ships one concrete, dependency-free piece of that design now:
DenyEscalationTracker locks out an actor who repeatedly triggers
arg_constraint/credential_exfil denies within a short window, closing
the gap where a probing client could retry indefinitely at whatever
rate the existing rate limiter otherwise allows. Wired through
CapabilityService, on by default, configurable via
QONTO_DENY_ESCALATION_* env vars. Ordinary denies (authz_denied,
tenant_scope) never count toward it.

Also adds specs/security-genome.yaml (kings-guard's genome-record
shape, populated now so no rework is needed once a consumer exists).

Verified: pytest -> 39 passed (8 new); REST and MCP smoke scripts both
pass against fixtures; compileall clean.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-23 22:59:06 +02:00
docs Add SecurityPractice.md, Security Genome record, and deny-escalation lockout 2026-07-23 22:59:06 +02:00
research Bootstrap qonto-assistant: intent, blueprint, research, workplans 2026-07-21 23:32:24 +02:00
scripts QONTO-WP-0003-T06: MCP smoke script + operator runbook update 2026-07-23 11:04:39 +02:00
specs Add SecurityPractice.md, Security Genome record, and deny-escalation lockout 2026-07-23 22:59:06 +02:00
src/qonto_assistant Add SecurityPractice.md, Security Genome record, and deny-escalation lockout 2026-07-23 22:59:06 +02:00
tests Add SecurityPractice.md, Security Genome record, and deny-escalation lockout 2026-07-23 22:59:06 +02:00
workplans QONTO-WP-0003-T07: close out Phase 2 MCP workplan 2026-07-23 13:56:06 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-07-23 13:56:27 +02:00
.gitignore Bootstrap qonto-assistant: intent, blueprint, research, workplans 2026-07-21 23:32:24 +02:00
.repo-classification.yaml Complete Phase 1: policy kernel, REST service, and local smoke tooling 2026-07-22 21:21:05 +02:00
AGENTS.md Complete Phase 1: policy kernel, REST service, and local smoke tooling 2026-07-22 21:21:05 +02:00
INTENT.md Seeded intent and initial workplan 2026-07-22 00:31:50 +02:00
LICENSE Initial commit 2026-07-21 21:19:44 +00:00
Makefile Complete Phase 1: policy kernel, REST service, and local smoke tooling 2026-07-22 21:21:05 +02:00
pyproject.toml QONTO-WP-0003-T01: MCP adapter skeleton on shared capability core 2026-07-22 21:41:24 +02:00
README.md QONTO-WP-0003-T07: close out Phase 2 MCP workplan 2026-07-23 13:56:06 +02:00
SCOPE.md Bootstrap qonto-assistant: intent, blueprint, research, workplans 2026-07-21 23:32:24 +02:00
WORK-RECORDS.md chore(consistency): sync WORK-RECORDS.md for QONTO-WP-0003 closure [auto] 2026-07-23 13:56:38 +02:00

README.md

qonto-assistant

Policy-governed Qonto domain API and MCP assistant for Binky (and later multi-tenant dogfood).

One choke point for bank access across every coding agent and harness. Clients never hold the Qonto API key. v1 policy: read for awareness only — no spend, no volume-cost actions.

Start here

Doc What
INTENT.md Why this exists; boundaries
specs/ArchitectureBlueprint.md Architecture, phases, policy model
research/2026-07-21-mcp-gateway-and-governed-domain-assistant.md External + internal research
docs/operator-runbook.md How to run and verify Phase 1 (REST)
docs/mcp-integration.md How to run and verify Phase 2 (MCP)

Status

Phase 1 runtime is implemented:

  • Python 3.12 service under src/qonto_assistant/
  • default-deny YAML policy
  • Qonto read-only client (organization, transactions)
  • REST endpoints: /v1/health, /v1/accounts, /v1/transactions, /v1/snapshot
  • audit metadata, rate limiting, concurrency bounds, tests

Phase 2 (MCP surface, workplans/QONTO-WP-0003-mcp-surface.md) is finished: a streamable-HTTP MCP adapter is mounted at /mcp on the same capability core and policy kernel as REST — proven identical by test, not just by construction (tests/test_policy.py, tests/test_audit_parity.py) — with tools qonto_org_summary, qonto_list_transactions, and qonto_cost_run_rate_hints. The endpoint is gated by a shared-secret bearer token (QONTO_ASSISTANT_MCP_TOKEN); see docs/mcp-integration.md for the auth model, its explicit gap vs. the OIDC/workload target (no issuer exists in this fleet yet), and the shared multi-harness client config snippet. The finance-qonto-read agent-harness tool profile is documented (qonto-assistant side) but not yet registered in agent-harness itself — separate repo, separate workplan.

Current verification:

  • PYTHONPATH=src ../state-hub/.venv/bin/python -m pytest → 31 passed
  • python3 -m compileall src tests scripts
  • ../state-hub/.venv/bin/python scripts/smoke_rest_api.py --python ../state-hub/.venv/bin/python
  • ../state-hub/.venv/bin/python scripts/smoke_mcp.py --python ../state-hub/.venv/bin/python

Local fixture-backed smoke mode is available through QONTO_FIXTURE_DIR, so the service can be exercised without real Qonto credentials. The REST smoke checks both a 31-day recent snapshot and a 90-day recurring-cost snapshot; the MCP smoke additionally exercises the bearer-token auth gate and an out-of-catalog tool deny path.

Phase 3 (flex-auth resource finance.qonto.read, graduated quotas, redaction profiles) is not started — see workplans/QONTO-WP-0003-mcp-surface.md closure notes for the seed.

Normal local workflow, when toolchain support exists:

make install-dev
make test
make run

Related

  • OpenBao lane: tenants/binky/qonto-api (ops-warden binky-qonto-api)
  • First pull / CostRunRate: binky-control BINKY-WP-0005