You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Browse filesBrowse the repository at this point in the historyBrowse files
iqdoctor
committed
Restrict exposed MCP tools for read-only operators
Use existing FastMCP ToolAnnotations as the source of truth so operators can narrow the client-visible surface without maintaining a separate tool allowlist.
Constraint: TELEGRAM_EXPOSED_TOOLS must default to all and accept only all or read-only.
Rejected: Hardcoded read-only tool-name allowlist | It would duplicate MCP annotations and drift from registered tool metadata.
Confidence: high
Scope-risk: narrow
Directive: Keep this as an MCP exposure filter; do not represent it as lowering Telegram session authority.
Tested: uv run pytest; uv run black --check .; git diff --check; smoke check confirmed read-only mode kept only readOnlyHint=True tools.
Not-tested: Live Telegram network behavior or mutation calls, by design.
0 commit comments