github.contributors

Top contributors to a repository, ranked by commit count: login, contributions, account type, and profile URL. Read-only; no caller key needed.

SERVERMcp SOURCE@2sio/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/io-github-2s-io-mcp/github.contributors.md

WHAT IT DOES

What github.contributors does on Mcp

AI agents call github.contributors to retrieve information from 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.contributors is rated Low

This tool queries public repository metadata (contributor statistics) and returns read-only data. It performs no modifications, executions, deletions, or financial operations. The explicit "Read-only" designation and lack of authentication requirements confirm this is a pure data retrieval operation with minimal risk.

From the tool's definition Tool description explicitly states "Read-only; no caller key needed" and retrieves "Top contributors to a repository, ranked by commit count: login, contributions, account type, and profile URL." These are information query operations with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github.contributors safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github.contributors, this is the rule to start with:

github.contributors Allowed

github.contributors 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.contributors": {}
  }
}

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

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

FAQ

Questions about github.contributors

What does the github.contributors tool do? +

Top contributors to a repository, ranked by commit count: login, contributions, account type, and profile URL. Read-only; no caller key needed. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on github.contributors? +

Register the MCP server in PolicyLayer and add a rule for github.contributors: 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 Mcp. Nothing to install.

What risk level is github.contributors? +

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

Can I rate-limit github.contributors? +

Yes. Add a rate_limit block to the github.contributors 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.contributors completely? +

Set action: deny in the PolicyLayer policy for github.contributors. 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.contributors? +

github.contributors is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 572 tools →

Across the catalogue

The MCP Attack Database →

Guides

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