Low Risk

getRepoDirectories

getRepoDirectories

How to control getRepoDirectories ↓

What getRepoDirectories does on Github Repo

AI agents call getRepoDirectories 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 getRepoDirectories needs a policy

This tool retrieves directory information from a GitHub repository without modifying, deleting, or executing anything. It is a query/fetch operation with no side effects, fitting the Read category. Low severity due to limited blast radius—directory listings are typically non-sensitive metadata and read-only access poses minimal risk.

From the tool's definition Tool name 'getRepoDirectories' indicates it retrieves directory listings from a repository. Sibling tools 'getRepoAllDirectories' and 'getRepoFile' are clearly Read operations (fetching repo structure and file contents), suggesting this tool follows the same…

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

How to control getRepoDirectories

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 getRepoDirectories:

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

getRepoDirectories 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 getRepoDirectories

What does the getRepoDirectories tool do? +

getRepoDirectories. 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 getRepoDirectories? +

Register the Github Repo MCP server in PolicyLayer and add a rule for getRepoDirectories: 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 getRepoDirectories? +

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

Can I rate-limit getRepoDirectories? +

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

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

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