ディレクトリ構造をツリー形式で可視化します
AI agents call visualize_directory_tree to retrieve information from Claude MCP Server Integration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a retrieval/query operation to display filesystem directory information in tree format. It has no side effects, creates no modifications, executes no code, and poses minimal security risk. It fits squarely within the Read category: it queries filesystem metadata and presents it visually, similar to the 'ls' or 'tree' commands used for inspection only.
From the tool's definition The description states "visualize_directory_tree" and is described as 'ディレクトリ構造をツリー形式で可視化します' (visualize directory structure in tree format).
Attacks that exploit this kind of access
ディレクトリ構造をツリー形式で可視化します. It is categorised as a Read tool in the Claude MCP Server Integration MCP Server, which means it retrieves data without modifying state.
Register the Claude MCP Server Integration MCP server in PolicyLayer and add a rule for visualize_directory_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 Claude MCP Server Integration. Nothing to install.
visualize_directory_tree is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the visualize_directory_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.
Set action: deny in the PolicyLayer policy for visualize_directory_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.
visualize_directory_tree is provided by the Claude MCP Server Integration MCP server (mokemoke0821/claude-mcp-integration). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →