repo_path
Path to Git repository (optional if default repository is configured) (string, optional)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/repo-path.md
What repo_path does on GitHub
AI agents call repo_path 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 repo_path is rated Low
This is a parameter or configuration option that identifies which repository to operate on, not an action that reads, writes, executes, or modifies data itself. It enables other tools to know which repo context to use. On its own, it has no side effects and does not retrieve data—it merely specifies a repository location.
From the tool's definition Tool name 'repo_path' and description indicate it specifies a path parameter to a Git repository. The description uses language consistent with a configuration/parameter tool ('optional if default repository is configured'), not an action that performs…
Attacks that exploit this kind of access
The rule that runs repo_path 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 repo_path, this is the rule to start with:
repo_path 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 repo_path call is checked against it from then on.
Questions about repo_path
Path to Git repository (optional if default repository is configured) (string, optional). 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 repo_path: 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.
repo_path 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 repo_path 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 repo_path. 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.
repo_path 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