get_file_contents
Get the contents of a file or directory from a GitHub repository
This record as markdown: /tools/github/get-file-contents.md
What get_file_contents does on GitHub
AI agents call get_file_contents to retrieve information from GitHub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
ref | string | — | Accepts optional git refs such as `refs/tags/{tag}`, `refs/heads/{branch}` or `refs/pull/{pr_number}/head` |
sha | string | — | Accepts optional commit SHA. If specified, it will be used instead of ref |
path | string | — | Path to file/directory |
repo | string | — | Repository name |
owner | string | — | Repository owner (username or organization) |
Parameters from the server's own tool schema.
Why get_file_contents is rated Low
This tool retrieves file or directory contents from a repository without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal blast radius—an AI agent misusing it could only access files it has permission to view, not modify or delete them.
From the tool's definition Tool name 'get_file_contents' and description 'Get the contents of a file or directory from a GitHub repository' explicitly indicate data retrieval with no modifications or side effects.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs get_file_contents safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_file_contents, this is the rule to start with:
get_file_contents is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every get_file_contents call is checked against it from then on.
Questions about get_file_contents
Get the contents of a file or directory from a GitHub repository. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
get_file_contents accepts 5 parameters: ref, sha, path, repo, owner. The full parameter table on this page comes from the server's own tool schema.
Register the GitHub MCP server in PolicyLayer and add a rule for get_file_contents: 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. Nothing to install.
get_file_contents 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_file_contents 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_file_contents. 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_file_contents is provided by the GitHub MCP server (oci:ghcr.io/github/github-mcp-server:1.3.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue