github_list_repos

A read tool on the Integrations MCP server.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-mcp

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/shriram-vasudevan-integrations-mcp/github-list-repos.md

WHAT IT DOES

What github_list_repos does on Integrations MCP

AI agents call github_list_repos to retrieve information from Integrations MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why github_list_repos is rated Low

This tool retrieves repository information from GitHub—a non-destructive query operation. Although the description is empty, the name unambiguously indicates a data retrieval function. Even on a multi-tool platform with broad API coverage, listing repositories has no write, execute, or destructive capabilities.

From the tool's definition Tool name 'github_list_repos' indicates listing/querying GitHub repositories. The 'list' verb and repository querying operation are characteristic of Read operations that retrieve data without side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github_list_repos safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, 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 Allowed

github_list_repos is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "github_list_repos": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every github_list_repos call is checked against it from then on.

FAQ

Questions about github_list_repos

What does the github_list_repos tool do? +

github_list_repos is a read tool on the Integrations MCP server. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on github_list_repos? +

Register the Integrations 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 Integrations MCP. 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 Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Integrations, and thousands of servers like it.

This server

All 420 Integrations tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →