OAuth scopes
The consent screen offers two levels. Full access grants the mcp scope; read-only grants mcp:read, which permits only tools marked read-only. The choice belongs to the operator, not to the client. An OAuth connection also acts as the user who approved it: it reaches only what that user's role and modules allow, and stops working if the user is removed.
Confirmation-gated tools
Tools flagged "needs confirmation" in the reference — for example messages.send, folio.closeFolio, checkin.revokeForStay and smart-locks.unlock — require _confirm: true in the arguments. Omit it and the call is refused rather than performed. Not every tool with a real-world effect is gated (inbox.send_reply sends to a guest without it), so check the flag per tool.
Read-only by design
In the sensitive areas the split is deliberate: an agent may look, but not change. api_keys.list returns names, prefixes and usage timestamps — never a secret — and there is no tool to create or revoke a key, because a key that could mint or kill its siblings is a privilege-escalation path. webhooks.list returns URLs and delivery timestamps but never the signing secret, and there is no tool to add or repoint a subscription. billing.summary reads the subscription state; Checkout and the billing portal stay in the web UI. OAuth grant administration is not exposed at all.