get_user_detail
AI agents call get_user_detail to retrieve information from GitHub MCP Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user details from GitHub Enterprise without modifying any data. While the description is empty, the name clearly indicates a getter/retrieval operation, and all sibling tools on this server are read-only queries. The potential blast radius is limited to information disclosure, which is typical low-risk for read operations.
From the tool's definition Tool name 'get_user_detail' indicates retrieval of user information. Server description confirms this MCP server provides 'access to enterprise users, organizations, emails, and license information.' Sibling tools (get_user_enterprise_roles,…
Attacks that exploit this kind of access
get_user_detail. It is categorised as a Read tool in the GitHub MCP Bridge MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP Bridge MCP server in PolicyLayer and add a rule for get_user_detail: 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 Bridge. Nothing to install.
get_user_detail 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_detail 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_detail. 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_detail is provided by the GitHub MCP Bridge MCP server (vipink1203/mcp-github-enterprise). 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 →