Reads the content of a specified file within the active repository.
AI agents call read_file_in_repo to retrieve information from Git PR MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query/fetch operation that retrieves file content from a repository without side effects. It matches the 'Read' category definition: retrieves or queries data with no side effects. The low severity reflects minimal blast radius—an AI agent misusing this tool could only expose repository contents it already has access to, not cause damage or unauthorized actions.
From the tool's definition Tool name 'read_file_in_repo' and description 'Reads the content of a specified file within the active repository' indicate data retrieval with no modification or deletion.
Attacks that exploit this kind of access
Reads the content of a specified file within the active repository. It is categorised as a Read tool in the Git PR MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Git PR MCP Server MCP server in PolicyLayer and add a rule for read_file_in_repo: 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 Git PR MCP Server. Nothing to install.
read_file_in_repo 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 read_file_in_repo 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 read_file_in_repo. 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.
read_file_in_repo is provided by the Git PR MCP Server MCP server (peterj/git-pr-mcp). 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 →