github_get_pr_files
AI agents call github_get_pr_files to retrieve information from GitHub Code Review Assistant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves file information associated with a pull request—a read-only operation with no side effects. It does not modify, delete, or execute anything. The blast radius of misuse is minimal since it only exposes existing PR file metadata that developers already have access to through GitHub's UI.
From the tool's definition Tool name 'github_get_pr_files' indicates retrieval of pull request file data. The empty description limits certainty, but the naming pattern and sibling tools (github_get_pr_details, github_get_pr_diff, github_get_pr_comments) all perform read-only GitHub…
Attacks that exploit this kind of access
github_get_pr_files. It is categorised as a Read tool in the GitHub Code Review Assistant MCP Server, which means it retrieves data without modifying state.
Register the GitHub Code Review Assistant MCP server in PolicyLayer and add a rule for github_get_pr_files: 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 Code Review Assistant. Nothing to install.
github_get_pr_files 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_pr_files 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_pr_files. 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_pr_files is provided by the GitHub Code Review Assistant MCP server (sanjanaspanda/mcp-server). 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 →