MCP server design (read-only v1)

Tool surface, schemas, authorization model and audit events.

AdvancedCOMMUNITY ANALYSISMCPTypeScript

Design an MCP server exposing read-only access to {system}.
List the tools, their JSON input schemas, the authorization model per tool, rate limits and the audit events emitted.
Explicitly mark any tool that mutates state — we are not shipping those in v1. Note what an attacker could learn from combining tool outputs.

Use Case

Exposing internal read-only context to a tool-connected assistant.

Expected Result

A tool inventory with schemas and an explicit authorization model.