getRepoActivity
AI agents call getRepoActivity to retrieve information from GitHubMcpServer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get' prefix combined with context of a GitHub API tool that lists repository operations indicates this reads/queries activity data. No modification, deletion, or execution capability is implied. Empty description prevents higher confidence, but the tool name and API pattern strongly suggest a Read operation with low blast radius if misused by an agent.
From the tool's definition Tool name 'getRepoActivity' indicates data retrieval with 'get' prefix. Description is empty, which limits confidence, but the naming convention and sibling tools (create/update/get operations) suggest this retrieves repository activity metadata without…
Attacks that exploit this kind of access
getRepoActivity. It is categorised as a Read tool in the GitHubMcpServer MCP Server, which means it retrieves data without modifying state.
Register the GitHubMcpServer MCP server in PolicyLayer and add a rule for getRepoActivity: 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 GitHubMcpServer. Nothing to install.
getRepoActivity 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 getRepoActivity 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 getRepoActivity. 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.
getRepoActivity is provided by the GitHubMcpServer MCP server (moksh555/githubmcpserver). 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 →