user
Username to get teams for. If not provided, uses the authenticated user. (string, optional)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/user.md
What user does on GitHub
AI agents call user 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.
Why user is rated Low
This tool queries and retrieves team membership data based on a username parameter. It performs a read-only operation with no capability to modify, delete, or execute actions. The blast radius of misuse is minimal—an attacker could enumerate teams but cannot alter data, trigger workflows, or access sensitive resources beyond what the authenticated user already can view.
From the tool's definition Tool description indicates it retrieves team information for a given username or the authenticated user—'Username to get teams for' and 'uses the authenticated user'—which is a data retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs user 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 user, this is the rule to start with:
user 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 user call is checked against it from then on.
Questions about user
Username to get teams for. If not provided, uses the authenticated user. (string, optional). 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 user: 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.
user 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 user 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 user. 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.
user 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.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue