get_teams
Get details of the teams the user is a member of. Limited to organizations accessible with current credentials
This record as markdown: /tools/github/get-teams.md
What get_teams does on GitHub
AI agents call get_teams to retrieve information from GitHub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
user | string | — | Username to get teams for. If not provided, uses the authenticated user. |
Parameters from the server's own tool schema.
Why get_teams is rated Low
This tool queries and retrieves team membership information accessible to the authenticated user. It performs a read-only operation with no ability to modify, delete, or execute actions. The blast radius is minimal as it only exposes already-accessible organizational data.
From the tool's definition Tool name 'get_teams' and description 'Get details of the teams the user is a member of' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_teams safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_teams, this is the rule to start with:
get_teams is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every get_teams call is checked against it from then on.
Questions about get_teams
Get details of the teams the user is a member of. Limited to organizations accessible with current credentials. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
get_teams accepts 1 parameter: user. The full parameter table on this page comes from the server's own tool schema.
Register the GitHub MCP server in PolicyLayer and add a rule for get_teams: 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. Nothing to install.
get_teams 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_teams 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_teams. 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_teams is provided by the GitHub MCP server (oci:ghcr.io/github/github-mcp-server:1.3.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue