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:
1 parent
dee883472a
commit
059a1da375
10 files changed
+175
-26
No files matched your search
@@ -184,7 +184,12 @@ brokeless is an MCP server too, so an AI app like Claude Code can read your mone
|
||||
|
||||
3. Start a new Claude Code session and ask, for example: "Which of my brokeless rules catch too much?"
|
||||
|
||||
It is summary only, like broke ai: rounded amounts, months not days, names as placeholders (⟨M1⟩, ⟨A1⟩), never single transactions. Changes act on your real data, and Claude says what it will change first. Revoke a token on the same page. With AI switched off in Settings the endpoint refuses.
|
||||
When you make a token you choose what it sees:
|
||||
|
||||
- **Summary** (default): like broke ai. Rounded amounts, months not days, names as placeholders (⟨M1⟩, ⟨A1⟩), never single transactions.
|
||||
- **Full detail**: real names, exact amounts, dates and single transactions with their id, so Claude can fix rows one by one (`list_transactions`, `update_transactions`, `mark_transfer_pair`). IBANs and account numbers stay shortened (`NL24…5339`). Your real transactions then go to Anthropic while you use it, so brokeless asks you to confirm that.
|
||||
|
||||
A token only ever reaches its own user: every call runs in that user's session and every tool filters on that user too, so a partner's shared accounts don't show either. Changes act on your real data, and Claude says what it will change first. Revoke a token on the same page. With AI switched off in Settings the endpoint refuses.
|
||||
|
||||
## How AI stays private
|
||||
|
||||
|
||||
Reference in new issue
Block a user