Recursive directory tree as JSON, ignoring common hidden/ignored dirs.
AI agents call get_file_tree to retrieve information from Cursor MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves filesystem metadata (directory structure) in a read-only fashion. It matches the Read category definition: retrieves or queries data with no side effects. The low severity reflects minimal blast radius—an AI agent misusing this tool could only enumerate directory structures, creating no destructive or operational harm.
From the tool's definition Tool description: 'Recursive directory tree as JSON, ignoring common hidden/ignored dirs.' — purely retrieves and queries filesystem structure with no modifications, no code execution, and no side effects.
Attacks that exploit this kind of access
Recursive directory tree as JSON, ignoring common hidden/ignored dirs. It is categorised as a Read tool in the Cursor MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cursor MCP Server MCP server in PolicyLayer and add a rule for get_file_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 Cursor MCP Server. Nothing to install.
get_file_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 get_file_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 get_file_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.
get_file_tree is provided by the Cursor MCP Server MCP server (tariqnasheed/cursor_mcp_server). 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 →