auth_connect

SERVERRokha SOURCEhttps://rokha.ai/mcp/jsonrpc

Medium RISK CLASS

Category Write

Parameters 20 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-rokha-rokha/auth-connect.md

WHAT IT DOES

What auth_connect does on Rokha

AI agents use auth_connect to create or update resources in Rokha, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rokha environment.

Parameter	Type	Required	Description
`provider`	string	—	Tier-1 provider id (mutually exclusive with server_url).
`server_url`	string	—	Any MCP server URL for the spec handshake.

Parameters from the server's own tool schema.

RISK

Why auth_connect is rated Medium

Initiates OAuth flow and stores credentials in vault; reversible write action.

From the tool's definition Start an OAuth Connect, token lands in the vault

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs auth_connect safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Rokha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For auth_connect, this is the rule to start with:

auth_connect Rate-limited

auth_connect stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "auth_connect": {
      "limits": [
        {
          "counter": "auth_connect_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every auth_connect call is checked against it from then on.

FAQ

Questions about auth_connect

What does the auth_connect tool do? +

Start an OAuth Connect and get the consent URL to open in a browser. Pass provider (github|google|x|atlassian|microsoft|slack|notion|gitlab|discord|reddit|linear — account-wide, reused everywhere) OR server_url (any MCP server; Rokha runs the MCP auth-spec handshake, grant bound to that server). On approval the token lands in the vault under the returned alias. Requires a logged-in identity. It is categorised as a Write tool in the Rokha MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does auth_connect accept? +

auth_connect accepts 2 parameters: provider, server_url. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on auth_connect? +

Register the Rokha MCP server in PolicyLayer and add a rule for auth_connect: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Rokha. Nothing to install.

What risk level is auth_connect? +

auth_connect is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit auth_connect? +

Yes. Add a rate_limit block to the auth_connect rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block auth_connect completely? +

Set action: deny in the PolicyLayer policy for auth_connect. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides auth_connect? +

auth_connect is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Rokha, and thousands of servers like it.

This server

All 216 Rokha tools →

Across the catalogue

connect-gmail on Meme MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →