get_files
Get the list of files changed in a pull request. Use with pagination parameters to control the number of results returned.
This record as markdown: /tools/io-github-aifity-omnigit-mcp/get-files.md
What get_files does on GitHub
AI agents call get_files 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.
Why get_files is rated Low
This tool retrieves metadata about files in a pull request without creating, modifying, deleting, or executing any code. It is a straightforward read operation with minimal blast radius even if invoked arbitrarily by an AI agent.
From the tool's definition Tool name 'get_files' and description 'Get the list of files changed in a pull request' indicates retrieval of data with no modification capability.
Attacks that exploit this kind of access
The rule that runs get_files 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_files, this is the rule to start with:
get_files 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_files call is checked against it from then on.
Questions about get_files
Get the list of files changed in a pull request. Use with pagination parameters to control the number of results returned. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP server in PolicyLayer and add a rule for get_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. Nothing to install.
get_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 get_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 get_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.
get_files is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.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