Low Risk

github_get_user_info

Get information about a specific GitHub user

How to control github_get_user_info ↓

AI agents call github_get_user_info to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves publicly or user-accessible GitHub profile information. It performs a query operation that does not create, modify, delete, or execute code. The blast radius of misuse is minimal: an agent could enumerate users or profile data, but cannot alter state, delete data, move money, or trigger external actions. Classified as Read/low severity.

From the tool's definition Tool name contains 'get' and description states 'Get information about a specific GitHub user' — a pure data retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access github_get_user_info gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for github_get_user_info:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "github_get_user_info": {}
  }
}

github_get_user_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Sage MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the github_get_user_info tool do? +

Get information about a specific GitHub user. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on github_get_user_info? +

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

What risk level is github_get_user_info? +

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

Can I rate-limit github_get_user_info? +

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

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

github_get_user_info is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sage MCP tool call.

Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.