Permissions
Permissions
Any of the account-scoped tools (all but list_accounts) can be forbidden for
a given account with disabled_tools in config.toml:
[accounts.personal]
provider = "generic"
email = "you@fastmail.com"
host = "imap.fastmail.com"
disabled_tools = ["get_attachment"]
A blocked call returns a plain string to the model:
Error: 'get_attachment' is disabled for account 'personal'
rather than failing silently, so the assistant can tell you what happened instead of guessing.
The toggleable tools
| Name | Label in the settings window |
|---|---|
list_folders | List folders |
list_messages | Browse messages |
search_messages | Search messages |
read_message | Read a message |
get_attachment | Download attachments |
list_accounts is deliberately not in the list: it has no per-account scope —
it is the tool that tells you which accounts exist.
From the settings window
Rather than editing TOML by hand, open the
settings window on its Permissions tab — a
grid of accounts and tools where unticking a box and saving writes
disabled_tools back into config.toml. rubit-mcp-mail permissions opens it
there directly.
The window shows what is allowed; the file stores what is forbidden.
Untick everything you don't want and the inverse is written for you. An empty
result removes the key entirely rather than writing disabled_tools = [].
The one caveat
serve process caches its config on first read, so toggling a permission
does not affect a running MCP server — one launched by Claude Desktop, say —
until it is restarted.Why this exists
Today every tool is a read, so this is about narrowing what an assistant can reach rather than preventing damage: keeping attachments off a shared account, or keeping a work mailbox listed but unreadable. It is also the mechanism any future write tool would be gated behind.
There is no delete or trash tool, and none is planned. See Security for what the server can and cannot do.