ReadOnly
The read surface of the JSON Ledger API — an allowlist of method + path prefix, not a rule about HTTP verbs.
That distinction is the whole point. An earlier version of this policy allowed GET and nothing else, on the usual HTTP convention that GET is the safe verb. Canton's JSON Ledger API does not follow that convention: the ACS query is POST /v2/state/active-contracts, update reads are POST /v2/updates…, and event lookup is POST /v2/events/events-by-contract-id. Under a GET-only rule a dApp could read the ledger end and the synchronizer list and essentially nothing else — including, fatally, not its own holdings, which a token-standard dApp needs to choose input UTXOs.
Meanwhile GET is not reliably safe either: POST /v2/packages uploads a DAR, so a verb-shaped rule gets the risk backwards in both directions.
What stays denied, by simply not being listed: command submission and interactive submission (prepare/execute — a dApp reaches those through prepareExecute, where they are approved and hash-verified), DAR upload, package vetting, and every user/party/identity-provider surface, which can grant rights and allocate parties.