MCP rights: what an agent may do
Three rights per server, independent of each other, and the rule for when a click is needed. In OAuth the rights are the scopes, under the same names.
Last updated:
A connection belongs to one of the two servers and carries a subset of its three rights; every tool and event requires exactly one, the market tools the base right. The names stay German because they are the scope names: lesen (read), vorschlagen (propose), freigeben (approve), suchen (search), suchauftraege (search briefs), anfragen (enquiries).
When a click is needed
The model prepares, a person carries out. Read-only calls run at once. What only changes your office or account runs at once (creating something new, filling gaps); anything that would replace an existing value becomes a suggestion or waits for a click. For anything consequential (goes out, overwrites, deletes), in this order:
- Always with a click: deleting, merging, setting an approval level, switching an auto mode on.
- Without a click if your office has set the kind to Automatic in the app (Approval levels) and the connection carries the boundary right (
freigeben); it then shows up in the log. - Otherwise with a click in a card in the chat. Without the right the card leads to the app with Approve in Athaus.
If the kind is Off, the connection prepares nothing. The model never approves itself: the click is a tool of its own that only the card calls (confirmation card). Search has no level: an enquiry to a provider only goes out with your click and needs anfragen.
Athaus für Anbieter
Address: https://anbieter.mcp.athaus.ai/mcp
lesen
Read everything your office sees in the app: properties, enquiries, valuations and what is due today, plus the market tools. Without this right the connection opens nothing, so it is always on.
Tools: get_briefing, search_properties, get_property, search_inquiries, get_inquiry, list_proposals, list_viewings, search_contacts, get_contact, list_tasks, get_valuation, check_location, estimate_value, count_demand, calculate_purchase_costs.
Events: inquiry.received, message.received, viewing.booked, viewing.cancelled, proposal.pending, file.processed, viewing.upcoming.
vorschlagen
Prepare: fill in property details, draft replies, create valuations. Anything that would replace an existing value waits as a suggestion for a yes. With this right alone nothing goes out.
Tools: save_property, publish_listing, unpublish_listing, update_inquiry, draft_reply, save_viewing, save_availability, save_contact, save_list, save_task, save_note, save_valuation, share_owner_report, update_automation, delete_item.
Events: none.
freigeben
Decide on a suggestion and accept your click in the assistant's card: a reply you approve there is sent to the enquirer. Whatever your office has set to Automatic in the app also runs through the connection without a click when it has this right. Without it you approve in the app. On the consent page it stays off until you switch it on yourself.
Tools: decide_proposal.
Events: none.
Athaus Immobiliensuche
Address: https://suche.mcp.athaus.ai/mcp
suchen
Search the catalogue, read an exposé, use the market tools and see your own search briefs, matches and enquiries. Without this right the connection opens nothing, so it is always on.
Tools: search_listings, show_listings, get_listing, list_inquiries, get_inquiry, list_saved_searches, list_matches, check_location, estimate_value, count_demand, calculate_purchase_costs.
Events: matches.new, reply.received, viewing.changed.
suchauftraege
Create, change and pause search briefs. This only changes your own account; nothing leaves Athaus this way.
Tools: favorite_listing, save_search, save_profile, delete_item.
Events: none.
anfragen
Prepare an enquiry about a listing. With your click in the assistant's card it is sent to the provider. On the consent page this right stays off until you switch it on yourself.
Tools: send_inquiry, update_inquiry, book_viewing, cancel_viewing, decide_match.
Events: none.
Where rights are granted
For an app on the consent page (Sign-in): the base right is on, the boundary right off until you switch it on. For a key when you create it (Keys); it only carries rights of Athaus für Anbieter.
Keep reading
How to set what Athaus may do on its own
The three levels Off, Ask first and Automatic for each kind of suggestion, the offer to switch to Automatic, and the log.
How the agent and approval work together
Athaus prepares replies and changes, and nothing goes out without your yes, unless you set it to Automatic yourself.
MCP sign-in: OAuth, consent and keys
OAuth 2.1 for apps such as Claude and ChatGPT, a key for your own agents. Every call requires a sign-in, and consent applies per server.