Fetch the authenticated user's GitHub profile.
AI agents call get_user_profile to retrieve information from Github-Oauth MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves profile information for an authenticated user. It is a read-only operation that fetches data without creating, modifying, deleting, or executing any actions. The data returned is limited to already-public user profile information accessible only after OAuth authentication. The blast radius of misuse is minimal—an agent could only read profile data it is already authorized to access.
From the tool's definition Tool name 'get_user_profile' and description 'Fetch the authenticated user's GitHub profile' indicate a retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
Fetch the authenticated user's GitHub profile. It is categorised as a Read tool in the Github-Oauth MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Github-Oauth MCP Server MCP server in PolicyLayer and add a rule for get_user_profile: 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-Oauth MCP Server. Nothing to install.
get_user_profile 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_profile 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_profile. 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_profile is provided by the Github-Oauth MCP Server MCP server (nikhil-patil-ri/mcp-github-oauth). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →