get_directory_contents

Lists the contents of a specific directory in a GitHub repository. Returns file names, types, and sizes.

SERVERNitrostack SOURCEnitrocloudofficial/nitrostack

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/nitrostack/get-directory-contents.md

WHAT IT DOES

What get_directory_contents does on Nitrostack

AI agents call get_directory_contents to retrieve information from Nitrostack 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_directory_contents is rated Low

Tool retrieves directory structure and metadata without modifying data or executing code.

From the tool's definition Lists the contents of a specific directory in a GitHub repository.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_directory_contents safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Nitrostack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_directory_contents, this is the rule to start with:

get_directory_contents Allowed

get_directory_contents 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_directory_contents": {}
  }
}

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

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

FAQ

Questions about get_directory_contents

What does the get_directory_contents tool do? +

Lists the contents of a specific directory in a GitHub repository. Returns file names, types, and sizes. It is categorised as a Read tool in the Nitrostack MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_directory_contents? +

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

What risk level is get_directory_contents? +

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

Can I rate-limit get_directory_contents? +

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

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

get_directory_contents is provided by the Nitrostack MCP server (nitrocloudofficial/nitrostack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nitrostack, and thousands of servers like it.

This server

All 697 Nitrostack tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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