username
Username to list starred repositories for. Defaults to the authenticated user. (string, optional)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/username.md
What username does on GitHub
AI agents call username 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 username is rated Low
This tool retrieves/queries data (listing starred repositories) without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal security risk. The optional nature and default to authenticated user further reduces risk. Low severity due to limited blast radius if misused - it would only list publicly available starred repository information.
From the tool's definition Tool description indicates this parameter is used to 'list starred repositories' - a read-only retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs username 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 username, this is the rule to start with:
username 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 username call is checked against it from then on.
Questions about username
Username to list starred repositories for. Defaults to 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 username: 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.
username 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 username 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 username. 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.
username 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