github_login

Authenticate via GitHub OAuth device flow. First call returns a code + URL to open; run it again after authorizing to finish. (Or set GITHUB_TOKEN to skip.)

SERVERGitHub SOURCE@abhishekmcp/github

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-abhishekkumar2021-github/github-login.md

WHAT IT DOES

What github_login does on GitHub

AI agents call github_login as a supporting operation in GitHub workflows.

RISK

Why github_login is rated Low

This tool performs authentication/authorization setup, not data retrieval, modification, execution, destruction, or financial operations. It initiates an OAuth device flow and completes token acquisition. While it grants access to GitHub resources, the tool itself does not read, write, execute, or destroy anything — it is purely a credential/session establishment mechanism.

From the tool's definition Authenticate via GitHub OAuth device flow. First call returns a code + URL to open; run it again after authorizing to finish.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github_login safely

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

github_login Rate-limited

github_login gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "github_login": {
      "limits": [
        {
          "counter": "github_login_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about github_login

What does the github_login tool do? +

Authenticate via GitHub OAuth device flow. First call returns a code + URL to open; run it again after authorizing to finish. (Or set GITHUB_TOKEN to skip.). It is categorised as a Other tool in the GitHub MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on github_login? +

Register the GitHub MCP server in PolicyLayer and add a rule for github_login: 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 GitHub. Nothing to install.

What risk level is github_login? +

github_login is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit github_login? +

Yes. Add a rate_limit block to the github_login 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 github_login completely? +

Set action: deny in the PolicyLayer policy for github_login. 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 github_login? +

github_login is provided by the GitHub MCP server (@abhishekmcp/github). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 16 GitHub tools →

Across the catalogue

tiktok_ads_login on TikTok Ads MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →