Get repository overview: stars, forks, open issues, language, description, last push.
AI agents call get_repo_stats to retrieve information from Mcp Github Pm without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns existing repository statistics without creating, modifying, deleting, or executing any operations. The data retrieved is public repository information already exposed in GitHub's UI. No reversible or irreversible changes occur, no code execution, and no financial impact. This is purely informational access, fitting the Read category at low severity.
From the tool's definition Tool retrieves repository metadata: 'stars, forks, open issues, language, description, last push' — all read-only queries with no side effects.
Attacks that exploit this kind of access
Get repository overview: stars, forks, open issues, language, description, last push. It is categorised as a Read tool in the Mcp Github Pm MCP Server, which means it retrieves data without modifying state.
Register the Mcp Github Pm MCP server in PolicyLayer and add a rule for get_repo_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 Mcp Github Pm. Nothing to install.
get_repo_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 get_repo_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 get_repo_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.
get_repo_stats is provided by the Mcp Github Pm MCP server (lordbasilaiassistant-sudo/mcp-github-pm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →