Skip to main content
Niblet MCP uses browser OAuth. Each token is valid only for the Niblet MCP endpoint and the permissions shown during authorization.

Choose what the client can access

How Niblet protects requests

  • Tokens must use the Niblet format and target the correct MCP endpoint.
  • Every tool checks its required OAuth scope.
  • Account and user identity come from the token, not from tool arguments.
  • Request bodies and rates are bounded.
  • Input schemas reject unknown or malformed fields.
  • Destructive tools require explicit confirmation strings.
  • Successful changes create account audit events.
  • Responses use no-store caching.

What MCP never receives

Wi-Fi details, physical enrollment values, device credentials, app credentials, provider tokens, Starlark source, local preview files, and publication approval remain outside MCP.
Use a read-only request first. Expand to write scopes only when the assistant needs to make a specific change.
Last modified on August 29, 2026