github_get_authenticated_user

What github_get_authenticated_user does on ScopeGate

AI agents call github_get_authenticated_user to retrieve information from ScopeGate without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why github_get_authenticated_user is rated Low

This tool retrieves information about the currently authenticated user on GitHub. It is a read-only query that returns user identity/profile data with no side effects, no code execution, and no data modification. The blast radius of misuse is minimal—an attacker learns who the authenticated account is, which is typically non-sensitive metadata already available via GitHub's public API.

From the tool's definition Tool name and description indicate it 'Get[s] the authenticated GitHub user' — a retrieval operation with no modification, deletion, or execution of code.

The rule that runs github_get_authenticated_user safely

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "github_get_authenticated_user": {}
  }
}

Questions about github_get_authenticated_user