AI agents call get_team_members to retrieve information from GitHub without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a list of team members from GitHub, which is a read-only operation that queries existing data without creating, modifying, or deleting anything. The blast radius if misused is minimal — an attacker could enumerate team membership but cannot directly harm systems or data.
From the tool's definition Tool name is 'get_team_members' and description is 'Get team members' — uses the verb 'Get' which indicates data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_team_members gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GitHub, and nothing reaches the server without passing your rules. This is the rule we recommend for get_team_members:
{
"version": "1",
"default": "deny",
"tools": {
"get_team_members": {}
}
}get_team_members is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get team members. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
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/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GitHub, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
245 GitHub tools catalogued and risk-classified — across an index of 43,000+ MCP servers.