The meta-tool pattern trades discoverability for context cost — a model must search before it can act, but the client only ever loads two definitions. What makes it safe here is that permissions are evaluated per call against the dashboard's own RBAC, so the executor cannot become a way around the roles you already configured. Scope admin is not a small grant, though; the boundary is the user's own permissions.
DocsBot's endpoint, using the meta-tool pattern: rather than a tool per operation, it exposes a search over its admin API catalogue and a generic executor.
- search — find the relevant admin API operations
- execute — run one with structured parameters, with DocsBot evaluating dashboard permissions at call time
- Alongside these, three portable Agent Skills packages: administration, documentation search and support
OAuth with dynamic client registration, scope admin. Role-based access control and dashboard permissions are evaluated live on every MCP action rather than at connection time.
Admin enables it, then paste and authorize — add the endpoint to your client, then approve the OAuth consent screen