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.
This record as markdown: /tools/crawlora-mcp/github-user.md
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.
Why github_user is rated Low
This tool retrieves publicly available information about a GitHub user. It performs a read-only query of profile data that the user has intentionally made public. There are no modifications, deletions, code executions, or financial implications. The risk is minimal since it only accesses information the user chose to publish.
From the tool's definition Tool description states 'Retrieve a GitHub user profile' and 'Returns a public GitHub user's profile plus user-published social links.' The verb 'Retrieve' and the scope limited to public profile data indicate data querying with no side effects.
Attacks that exploit this kind of access
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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
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.
Questions about 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. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
github_user accepts 1 parameter: username. Required: username. The full parameter table on this page comes from the server's own tool schema.
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.
github_user is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue