get_user_organizations
AI agents call get_user_organizations 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.
The tool retrieves organization membership or affiliation data for a user. No description is provided, but the naming convention and server context strongly suggest this is a read operation that returns existing data without modification, deletion, or external effects. The 'get_' prefix is a standard indicator of retrieval.
From the tool's definition Tool name 'get_user_organizations' follows a GET/list pattern typical of read-only retrieval operations. The server description emphasizes 'access to' GitHub Enterprise data including organizations, indicating query-only functionality.
Attacks that exploit this kind of access
get_user_organizations. 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_organizations: 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_organizations 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_organizations 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_organizations. 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_organizations 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 →