get_repository_tree

A read tool on the GitHub MCP server.

SERVERGitHub SOURCEoci:ghcr.io/aifity/omnigit-mcp:0.5.0

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-aifity-omnigit-mcp/get-repository-tree.md

WHAT IT DOES

What get_repository_tree does on GitHub

AI agents call get_repository_tree 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.

RISK

Why get_repository_tree is rated Low

This tool retrieves repository tree information (file structure, contents) without creating, modifying, or deleting any data. It is a read-only query operation with minimal security risk. Even if an AI agent misuses it by traversing sensitive file paths, no data can be altered or destroyed.

From the tool's definition Tool name 'get_repository_tree' and description 'Get repository tree' indicate retrieval of repository structure/metadata with no modification capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_repository_tree 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_repository_tree, this is the rule to start with:

get_repository_tree Allowed

get_repository_tree is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_repository_tree": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every get_repository_tree call is checked against it from then on.

FAQ

Questions about get_repository_tree

What does the get_repository_tree tool do? +

get_repository_tree is a read tool on the GitHub MCP server. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_repository_tree? +

Register the GitHub MCP server in PolicyLayer and add a rule for get_repository_tree: 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.

What risk level is get_repository_tree? +

get_repository_tree is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_repository_tree? +

Yes. Add a rate_limit block to the get_repository_tree 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.

How do I block get_repository_tree completely? +

Set action: deny in the PolicyLayer policy for get_repository_tree. 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.

What MCP server provides get_repository_tree? +

get_repository_tree 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.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 245 GitHub tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →