github_list_repos

List repositories for the authenticated user

SERVERScopeGate SOURCEhttps://mcp.scopegate.cloud/{api_key}
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about github_list_repos

What does the github_list_repos tool do? +

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.

How do I enforce a policy on github_list_repos? +

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.

What risk level is github_list_repos? +

github_list_repos is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit github_list_repos? +

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.

How do I block github_list_repos completely? +

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.

What MCP server provides github_list_repos? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of ScopeGate's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.