get_repo_prs
AI agents call get_repo_prs to retrieve information from GitHub Projects MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves pull requests from a repository, which is a read-only operation with no side effects. However, severity is medium rather than low because GitHub repositories can contain sensitive code, proprietary logic, or internal architectural details that could be exposed through indiscriminate PR retrieval.
From the tool's definition Tool name 'get_repo_prs' and sibling tools (get_project_details, get_project_iterations, get_repo_issues) indicate retrieval operations.
Attacks that exploit this kind of access
get_repo_prs. It is categorised as a Read tool in the GitHub Projects MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub Projects MCP Server MCP server in PolicyLayer and add a rule for get_repo_prs: 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 Projects MCP Server. Nothing to install.
get_repo_prs 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_prs 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_prs. 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_prs is provided by the GitHub Projects MCP Server MCP server (jamescalam/github-projects-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_repo_prs is one line of GitHub Projects MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →