Repo-relative directory tree, gitignore-aware. Use INSTEAD of
AI agents call get_file_tree to retrieve information from Code Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely queries and retrieves filesystem metadata (directory tree structure). It has no side effects, does not execute code, does not modify data, and does not delete anything. It is a read-only operation similar to listing files. The gitignore-awareness is still a read operation. This represents minimal risk if misused by an AI agent, as the worst outcome would be unnecessary file tree queries.
From the tool's definition Tool name 'get_file_tree' and description 'Repo-relative directory tree, gitignore-aware' indicate it retrieves and displays repository structure without modifying or executing anything.
Attacks that exploit this kind of access
Repo-relative directory tree, gitignore-aware. Use INSTEAD of. It is categorised as a Read tool in the Code Context MCP Server, which means it retrieves data without modifying state.
Register the Code Context 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 Code Context. 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 Code Context MCP server (nachogeinfor-ops/code-context). 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 →