Get information about the authenticated GitHub user
AI agents call get_my_info to retrieve information from GitHub MCP TypeScript SDK 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 user profile information without modifying, executing, or deleting any data. It is a straightforward read operation consistent with the 'Read' category (fetch/get pattern). Severity is low because exposure of authenticated user metadata poses minimal blast radius for an AI agent—no destructive, financial, or code execution capabilities are involved.
From the tool's definition Tool name 'get_my_info' and description 'Get information about the authenticated GitHub user' indicate a retrieval operation with no side effects. Returns user profile data only.
Attacks that exploit this kind of access
Get information about the authenticated GitHub user. It is categorised as a Read tool in the GitHub MCP TypeScript SDK Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP TypeScript SDK Server MCP server in PolicyLayer and add a rule for get_my_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 GitHub MCP TypeScript SDK Server. Nothing to install.
get_my_info 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_my_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.
Set action: deny in the PolicyLayer policy for get_my_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.
get_my_info is provided by the GitHub MCP TypeScript SDK Server MCP server (om-shree-0709/github-mcp-ts-sdk). 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 →