Low Risk

get_directory_structure

Get the directory structure of the shadcn-ui v4 repository

How to control get_directory_structure ↓

What get_directory_structure does on Shadcn Ui

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

Low Risk

Why get_directory_structure needs a policy

This tool retrieves and returns information about the directory layout of a public repository. It has no side effects, does not modify data, execute code, delete anything, or involve financial transactions. It is purely informational, consistent with other 'get_' and 'list_' tools on this MCP server which are all Read category operations for examining UI component libraries.

From the tool's definition Tool name 'get_directory_structure' and description 'Get the directory structure of the shadcn-ui v4 repository' indicate a retrieval operation that queries and returns structural information about a repository without modification.

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

How to control get_directory_structure

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

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

get_directory_structure 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 Shadcn Ui — 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 get_directory_structure

What does the get_directory_structure tool do? +

Get the directory structure of the shadcn-ui v4 repository. It is categorised as a Read tool in the Shadcn Ui MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_directory_structure? +

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

What risk level is get_directory_structure? +

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

Can I rate-limit get_directory_structure? +

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

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

get_directory_structure is provided by the Shadcn Ui MCP server (jpisnice/shadcn-ui-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Shadcn Ui tool call.

Start from Shadcn Ui, 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.

10 Shadcn Ui 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.