github_get_traffic

Detailed 14-day traffic breakdown: views per day, top referrers, top paths.

SERVERGithub SOURCEdkeeno/github-mcp-server

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/dkeeno-github-mcp-server/github-get-traffic.md

WHAT IT DOES

What github_get_traffic does on Github

AI agents call github_get_traffic to retrieve information from Github 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_get_traffic is rated Low

This is a purely informational read operation that queries repository traffic statistics. It has no side effects, makes no modifications to code or configuration, and poses minimal risk even if misused by an AI agent — the worst outcome is exposure of public traffic analytics that repository owners can already see themselves.

From the tool's definition Tool retrieves 'detailed 14-day traffic breakdown: views per day, top referrers, top paths' — a query operation that returns analytics data without modifying, executing, or deleting anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github_get_traffic safely

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

github_get_traffic Allowed

github_get_traffic 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_get_traffic": {}
  }
}

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

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

FAQ

Questions about github_get_traffic

What does the github_get_traffic tool do? +

Detailed 14-day traffic breakdown: views per day, top referrers, top paths. It is categorised as a Read tool in the Github MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on github_get_traffic? +

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

What risk level is github_get_traffic? +

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

Can I rate-limit github_get_traffic? +

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

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

github_get_traffic is provided by the Github MCP server (dkeeno/github-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Github, and thousands of servers like it.

This server

All 69 Github tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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