get_team_members
Get member usernames of a specific team in an organization. Limited to organizations accessible with current credentials
This record as markdown: /tools/github/get-team-members.md
What get_team_members does on GitHub
AI agents call get_team_members 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 |
|---|---|---|---|
org | string | — | Organization login (owner) that contains the team. |
team_slug | string | — | Team slug |
Parameters from the server's own tool schema.
Why get_team_members is rated Low
This tool retrieves and queries team membership information without creating, modifying, deleting, or executing operations. It is a straightforward read operation with minimal security risk, constrained by existing credentials and access controls.
From the tool's definition Tool name 'get_team_members' and description 'Get member usernames of a specific team' indicates data retrieval with no modification.
Attacks that exploit this kind of access
The rule that runs get_team_members 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_team_members, this is the rule to start with:
get_team_members 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_team_members call is checked against it from then on.
Questions about get_team_members
Get member usernames of a specific team in an organization. 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_team_members accepts 2 parameters: org, team_slug. 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_team_members: 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_team_members 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_team_members 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_team_members. 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_team_members 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