Skip to main content
This page lists every tool the ngrok MCP server exposes, what each one does, and the scopes it needs. Use it to decide what to approve on the OAuth consent screen, or which scopes to give a personal access token.

How to read the tables

The Type column matches the markers the server sends to your client, which Make changes safely explains:
  • Read-only: The tool only reads data.
  • Changes: The tool creates or updates something in your account, or sends something on your behalf.
  • Destructive: The tool can delete, revoke, or break something that’s in use, so your client should always ask before it runs.
The Scopes column lists the scopes every call of the tool needs. If you signed in with OAuth and your token lacks one that your role allows, the server asks your client to sign in again to approve it. If your personal access token lacks one, the tool returns a scope error. A dash (—) means the tool needs no scope of its own. The ngrok API still checks your role and your scopes on every call, and some arguments need an extra scope. Some accounts see more tools than this page lists, such as tools for products in early access.

Account and team

To revoke an authtoken, API key, or SSH key, or to cancel an invitation, the AI agent uses delete_resource.

Endpoints, agents, and traffic

Domains, addresses, and certificates

IP policies

Vaults and secrets

Secret values never go through the chat. gw_create_secret and gw_update_secret send you a dashboard link where you type the value, and the dashboard checks your permissions when you save it.

Log exports

Get and delete any resource

Two tools work across resource types. The ID prefix picks the type, and the ngrok API checks the scope for that type. delete_resource can:
  • Delete a Cloud Endpoint, but not an Agent Endpoint or an AI Gateway endpoint.
  • Release a reserved domain or TCP address.
  • Delete an IP policy with all its rules, or one IP policy rule.
  • Delete an empty vault, or a secret.
  • Revoke an authtoken, API key, or SSH public key.
  • Cancel a pending team invitation.
  • Revoke an AI Gateway access key, or delete an AI Gateway access config, custom provider, provider key, virtual model, or firewall policy.

Documentation

These tools read the public ngrok documentation, so they need no scope.

AI Gateway

For the usage, request, capture, and model tools, such as aigw_list_usage and aigw_get_model, see AI Gateway tools. The tools in this section read and change your AI Gateway setup. A change applies to live traffic right away. Access key tokens and provider API keys never go through the chat: aigw_create_access_key, aigw_create_provider_key, and aigw_rotate_provider_key send you an AI dashboard link where you finish the step, so they need only a read scope on the token, and the dashboard checks your permissions when you save.

Feedback

Tools by scope

When you create a personal access token, give it the scopes for the tools you want your AI agent to use. A tool runs only when the token has every scope the tool lists. Some tools need no scope of their own, such as platform_whoami, gw_validate_traffic_policy, and the docs tools. get_resource and delete_resource need none either, but the ngrok API checks the token’s scopes for the type of object they read or delete.