get_file_contents
Read a file (decoded) or list a directory in a repo, at an optional ref.
This record as markdown: /tools/io-github-abhishekkumar2021-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 | — | Branch, tag, or commit SHA |
path | string | Yes | |
repo | string | Yes | Repository name |
owner | string | Yes | Repository owner (user or org) |
Parameters from the server's own tool schema.
Why get_file_contents is rated Low
This tool only retrieves and displays file contents or directory listings from a GitHub repository. It performs no creation, modification, deletion, code execution, or financial operations.
From the tool's definition Tool name is 'get_file_contents' and description states 'Read a file (decoded) or list a directory in a repo'. The verb 'Read' and the action of retrieving file contents without modification clearly indicate a data retrieval operation with no 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
Read a file (decoded) or list a directory in a repo, at an optional ref. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
get_file_contents accepts 4 parameters: ref, path, repo, owner. Required: 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 (@abhishekmcp/github). 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