github-repos
List GitHub repositories using upstream OAuth token
This record as markdown: /tools/frontmcp/github-repos.md
What github-repos does on Frontmcp
AI agents call github-repos to retrieve information from Frontmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why github-repos is rated Low
This tool retrieves data (list operation) with no side effects. The use of OAuth token for authentication is standard practice and doesn't change the read-only nature of the operation. The blast radius is minimal—misuse by an AI agent would only expose information the authenticated user has access to.
From the tool's definition Tool explicitly 'List GitHub repositories using upstream OAuth token' - a read-only query operation that retrieves repository data without modifying anything.
Attacks that exploit this kind of access
The rule that runs github-repos safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github-repos, this is the rule to start with:
github-repos 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 Frontmcp, apply this rule, and every github-repos call is checked against it from then on.
Questions about github-repos
List GitHub repositories using upstream OAuth token. It is categorised as a Read tool in the Frontmcp MCP Server, which means it retrieves data without modifying state.
Register the Front MCP server in PolicyLayer and add a rule for github-repos: 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 Frontmcp. Nothing to install.
github-repos 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 github-repos 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 github-repos. 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.
github-repos is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Front, and thousands of servers like it.
This server
Across the catalogue