Check who, what and which tool separately.
The problem
Tool names alone do not explain who may call a resource, which tools a profile exposes, or which OAuth scope permits the call.
An explanatory exhibit
One call through three checks
Local explanatory exhibit · invented records · no live service or agent call
Fictional request / read_notes
- 01 / IdentitySigned-in identity
Who is making this request?
- 02 / Resource scopenotes:read
May they use this resource?
- 03 / Tool profileread_notes selected
Is this tool exposed by the profile?
The permitted request continues to forwarding. One successful check does not stand in for the others.
Inspect the consequence
Missing resource scope
Stop at authorization
An authenticated identity alone is insufficient for the synthetic request.
Scope and profile agree
Forward the permitted call
Resource scope and tool visibility are distinct checks; the illustration uses fictional identities.
What this makes possible
The gateway separates authentication, resource scopes, owner-only routes and profile-based tool visibility while forwarding tool calls to connected MCP resources.
Source information sheet
Evidence, implementation & history Implementation inspected
What I checked
Source and release record inspected; no current product execution is claimed for this illustration.
Release anchor: v5.11.15.
Research cut: 14 October 2026. Source areas below are from panelforge-mcp. Private conversation references are retained in the research ledger and are not published here.
Implementation decisions
The gateway separates authentication, resource scopes, owner-only routes and profile-based tool visibility while forwarding tool calls to connected MCP resources.
Keep identity, OAuth authorization and tool catalog filtering as separate checks at the gateway boundary.
A path through the feature
- The consequence
Keep identity, OAuth authorization and tool catalog filtering as separate checks at the gateway boundary.
Source areas
src/permissions/permission-cache.tsconfig/resources.jsonsrc/proxy/proxy-mcp-handler.tssrc/auth/
The small explanatory exhibit uses invented records to describe the mechanism. Separate recordings and working examples carry their own evidence notes.
Recorded history
Dates describe the researched record, rather than today’s deployment.
v5.11.15