Low Risk

getRepoAllDirectories

getRepoAllDirectories

How to control getRepoAllDirectories ↓

What getRepoAllDirectories does on Github Repo

AI agents call getRepoAllDirectories to retrieve information from Github Repo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why getRepoAllDirectories needs a policy

This tool retrieves or lists directory information from a GitHub repository—a read-only operation with no ability to modify, delete, or execute. The blast radius is minimal; an AI agent misusing this tool could only access unwanted file structure information, not cause damage or side effects.

From the tool's definition Tool name 'getRepoAllDirectories' indicates it retrieves directory structures. Sibling tools 'getRepoDirectories' and 'getRepoFile' are clearly read operations.

Documented attack patterns abuse exactly the kind of access getRepoAllDirectories gives an agent:

How to control getRepoAllDirectories

PolicyLayer is an MCP gateway — it sits between your AI agents and Github Repo, and nothing reaches the server without passing your rules. This is the rule we recommend for getRepoAllDirectories:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "getRepoAllDirectories": {}
  }
}

getRepoAllDirectories is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Github Repo — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about getRepoAllDirectories

What does the getRepoAllDirectories tool do? +

getRepoAllDirectories. It is categorised as a Read tool in the Github Repo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getRepoAllDirectories? +

Register the Github Repo MCP server in PolicyLayer and add a rule for getRepoAllDirectories: 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 Repo. Nothing to install.

What risk level is getRepoAllDirectories? +

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

Can I rate-limit getRepoAllDirectories? +

Yes. Add a rate_limit block to the getRepoAllDirectories 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 getRepoAllDirectories completely? +

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

getRepoAllDirectories is provided by the Github Repo MCP server (ryan0204/github-repo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Github Repo tool call.

Start from Github Repo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

3 Github Repo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.