Separate read-only and write permissions for the Community MCP

Problem: Access to the Community MCP is tied to platform role, and write access comes with it automatically. Moderators and above can reply, publish, edit, close, and tag through an AI assistant, and there’s no way to turn that off. Teams that want analytics access for CSMs or marketers have to give them write access too.

Request:

1. A community-level setting to disable write tools, so the MCP can be offered as read-only.
2. Separate scopes for reading and writing, plus a read-only analytics scope that doesn’t need the Moderator or Admin role.

Why it matters: Least-privilege access is standard for tools connected to AI agents. Today the only safe option is to limit the MCP to a very small group.