AI and MCP

What Scopes Should an AI Connector Get on a Finance App?

A forum-style answer on MCP scopes for a finance app: what a scope is, why read-only comes first, and how to apply least privilege to an AI assistant.

Editorial illustration for What Scopes Should an AI Connector Get on a Finance App?

The question: what scopes does an AI assistant get when it connects to a finance app over MCP, and how do I keep that to the minimum? Short answer: a scope is the list of things the assistant is allowed to do, so you grant the smallest list that covers your task, start read-only, and widen it only when a real need appears.

First, what is a scope, in plain words?

When you connect an assistant to an app, the app asks you to approve access, and that approval carries a scope. Think of it as a permission slip with line items. Read transactions is one line. Change transactions is another. Delete is a third. The assistant can only do what the slip lists, however politely you ask it for more.

That is the useful part. A scope is enforced by the app, not by the assistant's good behaviour. SpendixAI lets you choose a scope when you connect Claude or ChatGPT over MCP, lets you begin read-only, and lets you disconnect at any time.

How do I decide what to grant?

  1. Write down the one job you want done, for example 'answer questions about my spending'.
  2. List the actions that job needs. Answering questions needs reading, nothing else.
  3. Pick the scope that matches that list and nothing wider.
  4. Try it for a week. If you hit a wall that really needs a write, widen the scope on purpose.
  5. When the job is done, disconnect. Do not leave a connector sitting there out of habit.

Can you show it with numbers?

Say your workspace holds 1,200 transactions and you ask the assistant to tidy up categories. With a read-only scope it can look at all 1,200 and tell you that, say, 40 rows look miscategorised. It can change none of them. You open the list of 40 and fix them yourself, or decide they are fine.

With a broader write scope the same request could change up to all 1,200 rows. If the assistant misreads a merchant name, one wrong rule could touch hundreds of rows before you notice. The read-only version caps the worst case at zero changes. That is the whole argument for least privilege: you are limiting the damage of a mistake, not predicting one.

Scope ideaCan readCan changeWorst case if it goes wrong
Read-onlyYes, within what you allowedNoIt misreads and says something wrong; nothing is altered
Read and editYesEdit existing rowsA wrong edit that you must find and undo
Broad writeYesAdd, edit, deleteMany rows altered or removed at once

Those three rows describe the idea in general. Check which options your app actually offers when you connect, and read each description before ticking it.

What does a scope not protect me from?

It does not control what the assistant tells you, or what the chat provider does with the conversation. Anything the assistant reads from your records appears in that chat, and the provider's own policies apply to it. A narrow scope reduces what can be read and changed; it does not make the chat private. So ask for summaries rather than pasting full lists, and review the provider's data settings separately.

What should I check after connecting?

  • Open the connection screen and confirm the scope shown is the one you picked.
  • Ask one test question you can verify, such as the total for a category you know.
  • Look at whether anything changed in your data; with read-only, nothing should.
  • Note how to disconnect before you need to.
  • Set a reminder a month later to review whether the connector is still useful.

My rule of thumb

Read-only for questions. A narrow edit scope only for a defined clean-up task,. And a disconnect when you are done. If a scope list ever asks for more than the task needs, that is a reason to say no, not to click through.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports