github_get_profile_stats
Aggregate profile stats: followers, public repos, total stars across owned repos.
This record as markdown: /tools/dkeeno-github-mcp-server/github-get-profile-stats.md
What github_get_profile_stats does on Github
AI agents call github_get_profile_stats 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.
Why github_get_profile_stats is rated Low
This tool queries public GitHub profile information and performs no write, destructive, execute, or financial operations. It is purely informational and read-only, presenting minimal risk even if misused by an agent.
From the tool's definition Tool retrieves aggregate profile statistics (followers, public repos, total stars) with no modifications or side effects. The description explicitly states it 'aggregates' and lists only data retrieval operations.
Attacks that exploit this kind of access
The rule that runs github_get_profile_stats 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_profile_stats, this is the rule to start with:
github_get_profile_stats 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 Github, apply this rule, and every github_get_profile_stats call is checked against it from then on.
Questions about github_get_profile_stats
Aggregate profile stats: followers, public repos, total stars across owned repos. It is categorised as a Read tool in the Github MCP Server, which means it retrieves data without modifying state.
Register the Github MCP server in PolicyLayer and add a rule for github_get_profile_stats: 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.
github_get_profile_stats 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_get_profile_stats 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_get_profile_stats. 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_get_profile_stats 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.
More on Github, and thousands of servers like it.
This server
Across the catalogue