Get a GitHub user
AI agents call get_user_id to retrieve information from GitHub Project MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about a GitHub user—a read-only operation that queries data without creating, modifying, or deleting anything. The low blast radius reflects minimal security risk if an agent calls this tool with arbitrary arguments (it simply returns user data, which is generally public on GitHub).
From the tool's definition Tool name is 'get_user_id' with description 'Get a GitHub user'. The verb 'get' combined with 'user' indicates data retrieval with no side effects.
Attacks that exploit this kind of access
Get a GitHub user. It is categorised as a Read tool in the GitHub Project MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub Project MCP Server MCP server in PolicyLayer and add a rule for get_user_id: 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 Project MCP Server. Nothing to install.
get_user_id 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_id 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_id. 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_id is provided by the GitHub Project MCP Server MCP server (jaqarx/github-project-mcp). 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 →