[mp-blurify]

Summary

• Add the agent-chat:use grant that a back-office AI assistant is gated on; the static and seeded admin roles hold it, and only the read-write level grants it.
• Add the payments.flow_daily and financial.summary analytics read tools (analytics:view).
• Add the withdrawals.queue (withdrawal:view) and players.deposit_compare (transaction:view) wallet read tools.
• IdentityReader gains an optional batched getUserIdsByPlayerIds; the comparison fails closed without it.
• Cover every new tool end to end through the MCP kernel, and record the tools and the player-id key rule in ADR-0042 and the wallet module doc.

Why

An assistant that answers an operator's questions reads platform tools through the MCP kernel on the asking admin's own grants. The tools so far are per player or narrow reports: the questions an operator asks first - how payments flowed this week, what waits in the withdrawal queue, which segment deposits less than last month, the financial summary of a period - had no tool. Core also had no grant to let an admin use such an assistant apart from running agents.

Every new tool is bounded (windows of at most 92 or 366 days, capped lists with a truncated flag or a hard limit), returns only allow-listed keys, and names a player only by player id under a playerId-style key, because consumers pseudonymise by key name. None returns a review note, address, transaction hash, username, email or user id.

Diagram

flowchart LR
  A[Admin's question] --> H[Assistant turn]
  H -->|tool call| K[MCP kernel]
  K -->|grant check on the admin's roles| G{granted?}
  G -->|no| F[forbidden, audited]
  G -->|yes| V[input contract: bounded windows and limits]
  V --> T[read tool: analytics or wallet]
  T --> R[allow-listed keys, playerId keys only]
  R --> H

Loading

Alternatives considered

• A generic query tool over the database: no grant per question, no redaction, unbounded reads.
• Serving the admin report routes as tools unchanged: they carry free text (review notes, addresses) and unbounded lists; the tools pick allow-listed keys and cap every list.
• Declaring the grant from the consumer's plugin: the IAM resource list is fixed in core, so the grant lives here.

Risks

• agent-chat:use is new: roles other than the static and seeded admin roles do not hold it until an operator grants it, and nothing checks it until a consumer gates on it.
• players.deposit_compare refuses a segment above 20 000 players (segment_too_large).
• A custom IdentityReader without getUserIdsByPlayerIds makes the deposit comparison fail closed.
• financial.summary keeps bonus cost as bonus money converted to cash, so NGR does not deduct cashback credits such as rakeback; the tool description says so. Whether NGR should deduct them is a separate decision.