get_user_enterprise_roles
AI agents call get_user_enterprise_roles 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 enterprise role information, which has no side effects—purely a read operation. However, severity is high because enterprise roles reveal access control hierarchy and permissions, making this valuable intelligence for an agent with malicious intent. The lack of a description increases risk slightly as function behavior cannot be fully verified, but the naming pattern and context are clear.
From the tool's definition Tool name indicates retrieval of user enterprise roles from GitHub Enterprise. Server description states it provides 'access to enterprise users, organizations, emails, and license information.' The 'get_' prefix and sibling tools (get_user_detail,…
Attacks that exploit this kind of access
get_user_enterprise_roles. 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_enterprise_roles: 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_enterprise_roles 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_enterprise_roles 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_enterprise_roles. 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_enterprise_roles 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 →