Get GitHub user information
AI agents call get_user to retrieve information from GitHub MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of GitHub user information. It retrieves publicly or authorized user data from the GitHub API with no capability to modify, delete, or execute actions. The sibling tools (create_repo, push_to_repo) perform write and execute operations, but this tool is strictly informational retrieval, making it the least risky category.
From the tool's definition Tool name is 'get_user' and description states 'Get GitHub user information', which retrieves data without modification or side effects.
Attacks that exploit this kind of access
Get GitHub user information. It is categorised as a Read tool in the GitHub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for get_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 GitHub MCP Server. Nothing to install.
get_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 get_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 get_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.
get_user is provided by the GitHub MCP Server MCP server (oghenetejiriorukpegmail/github-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_user is one line of GitHub MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →