MCP: full detail per token, single-transaction tools, one user per token

Tokens get a level (migration 0034). Summary stays the default; Full detail is
the person's explicit choice on Connect your AI, with a confirmation, and is
written into CLAUDE.md as the one exception to summary-only cloud AI. Full
tokens get the full tools plus list_transactions, update_transactions and
mark_transfer_pair; IBANs and long account numbers are shortened in everything
they return (ids stay intact).

Isolation tested with two users and an accepted partner share: RLS alone lets
the partner read the owner's shared rows, but every tool also filters on the
token's user, so nothing leaked and no change landed (own ids, rule id, names).

Also fixes the full spending_summary crashing on rows without a category.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
MangaValkandClaude Opus 5.5 committed 2026-11-19 21:36:12 +01:00
1 parent dee883472a
commit 059a1da375
10 files changed
+175 -26

No files matched your search

+1
View File
@@ -5,6 +5,7 @@ Personal finance app. Next.js 15 (app router), Supabase (sign-in, Postgres, row-
## Rules for any change
- **Bank data stays private.** Every AI path goes through `src/lib/llm/gate.ts`. A cloud model gets the summary only: rounded amounts, names replaced by tokens. Full detail goes only to a local model. Never add another path.
- One exception, the person's own explicit choice: an MCP token made with "Full detail" on Connect your AI (`src/app/api/mcp`, migration 0034). Summary stays the default, IBANs and account numbers stay shortened, and a token only ever reaches its own user's rows (their session, plus a `user_id` filter in every tool, so a partner's shared accounts never show).
- **No AI API keys.** AI runs on the person's own signed-in app (Claude Code, Codex, Gemini CLI, opencode), a local model, or their OpenRouter sign-in.
- **Tools stay off for prompts from a website.** The helper (`public/broke-connect.cjs`) only runs AI apps with no tools at all. Don't add one that can read files.
- **Every table has row-level security.** Secrets like `plaid_items.access_token` have no policies, so only the server's secret key reads them.