github_user

Retrieve a GitHub user profile. Returns a public GitHub user's profile plus user-published social links. Email is included only when the user has made it public on their profile.

SERVERCrawlora SOURCEcrawlora-mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/crawlora-mcp/github-user.md

WHAT IT DOES

What github_user does on Crawlora

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

Parameter	Type	Required	Description
`username`	string	Yes	GitHub username

Parameters from the server's own tool schema.

RISK

Why github_user is rated Low

Even though github_user only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github_user safely

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

github_user Allowed

github_user is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about github_user

What does the github_user tool do? +

Retrieve a GitHub user profile. Returns a public GitHub user's profile plus user-published social links. Email is included only when the user has made it public on their profile. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.

What parameters does github_user accept? +

github_user accepts 1 parameter: username. Required: username. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on github_user? +

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

What risk level is github_user? +

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

Can I rate-limit github_user? +

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

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

github_user is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Crawlora, and thousands of servers like it.

This server

All 728 Crawlora tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →