To disconnect an AI assistant from your finance app, open the app's list of connections, remove the assistant there, and then confirm that a fresh request from the assistant fails. Removing it only inside the assistant's own settings may leave the grant alive on the app's side. For a developer with several tools wired in, the cleanup does not end at that button.
Where do you start?
Start in the finance app, because that is where access is granted. SpendixAI lists MCP connections with a disconnect option, so you see which assistants are connected and can remove one at any time. If your app has no such list, treat that as a design problem and rotate whatever credential it used.
A five-step revoke
- Open the connection list in the finance app and note the assistant name and when it was connected
- Disconnect it
- In the assistant, remove the connector too, so it stops offering tools that will fail
- Ask the assistant to fetch last week's total; it should now fail or say it has no access
- Write the date and reason in your own notes
What else may still hold access?
| Place | What to look for | Action |
|---|---|---|
| Local config files | Server entries pointing at your finance app | Remove the entry and restart the client |
| Scripts and cron jobs | Anything that calls the app unattended | Disable, then delete or update |
| Other assistants | A second tool connected months ago | Check the connection list for every name |
| Browser sessions | Signed-in tabs on shared machines | Sign out, close the tab |
A worked check with hypothetical numbers
Say you disconnected at 4:00 pm after a session in which the assistant added three entries of ₹320, ₹780 and ₹1,150, a total of ₹2,250. Before you leave, open the day's transactions and confirm exactly three new rows with that total. If a fourth appears after 4:00 pm, something else is still connected, and you should look at your scripts.
Should you also tidy the data?
If the session made test entries, delete them. In SpendixAI, deleted transactions go to a recycle bin for 30 days, so a mistaken deletion can be recovered. Anything you imported by statement or typed by hand is unaffected by disconnecting; you are only closing the door, not removing the rooms.
What should you log for yourself?
Keep a small text file with one line per connection: assistant, scope, purpose, date connected, date removed. When you have three personal tools and a weekend project, this file is the only thing that tells you what should exist. Compare it with the app's list at each month start. Anything in the app that is not in your file is a question to answer today.
What about keys and tokens you made yourself?
If you ever created a long-lived key for a script, revoking an assistant's connection does not touch it. List every secret you generated for this app, find where each is stored, and replace the ones you no longer need. Search your repositories and notes for the app's name. A forgotten key in an old project is the quietest way for access to outlive your intention to remove it.
Prevent the next scramble
- Prefer read-only scope for anything that only needs to look
- Label each connection by purpose and date in your own notes
- Review the list on the first of every month
- Disconnect after one-off tasks, such as a year-end tidy up
- Never share logins or OTPs to repair a connection
Useful ideas start with a clearer picture of your own spending.
Explore your reports
