AI agents call get_file_tree to retrieve information from Code Merge MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves structural metadata about a project's file organization. It performs a read-only query with no capability to modify, execute, or delete data. The blast radius of misuse is minimal—an AI agent could only gain visibility into project structure, which poses no operational risk.
From the tool's definition Tool name 'get_file_tree' and description 'Retrieves the file tree structure of the project' indicate a query operation that returns data without modification or side effects.
Documented attack patterns abuse exactly the kind of access get_file_tree gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Code Merge MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_file_tree:
{
"version": "1",
"default": "deny",
"tools": {
"get_file_tree": {}
}
}get_file_tree is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieves the file tree structure of the project. It is categorised as a Read tool in the Code Merge MCP MCP Server, which means it retrieves data without modifying state.
Register the Code Merge 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 Merge MCP. 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 Merge MCP server (yy1588133/code-merge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Code Merge MCP, 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.
3 Code Merge MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.