github_list_repos
List repositories for the authenticated user
This record as markdown: /tools/io-github-alifanov-scopegate/github-list-repos.md
What github_list_repos does on ScopeGate
AI agents call github_list_repos to retrieve information from ScopeGate without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why github_list_repos is rated Low
This tool retrieves metadata about GitHub repositories belonging to the authenticated user. It is a query operation that produces no side effects, does not execute code, and does not modify or delete data. The only risk is exposure of repository metadata that may be considered sensitive (e.g., private repo names), but the blast radius is inherently limited to read-only information disclosure.
From the tool's definition Tool name contains 'list' and description explicitly states 'List repositories' — both indicate a retrieval operation with no data modification. The verb 'list' combined with 'authenticated user' confirms querying existing data.
Attacks that exploit this kind of access
The rule that runs github_list_repos safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_list_repos, this is the rule to start with:
github_list_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 ScopeGate, apply this rule, and every github_list_repos call is checked against it from then on.
Questions about github_list_repos
List repositories for the authenticated user. It is categorised as a Read tool in the ScopeGate MCP Server, which means it retrieves data without modifying state.
Register the ScopeGate MCP server in PolicyLayer and add a rule for github_list_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 ScopeGate. Nothing to install.
github_list_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_list_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_list_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_list_repos is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
This server
Across the catalogue