Low Risk

analyze_project

Analyze overall project structure. Args: project: Project name scan_depth: Depth of detailed analysis (higher is slower) ctx: Optional MCP context for progress reporting Returns: Project analysis

How to control analyze_project ↓

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

Low Risk

This is a code analysis tool that retrieves and queries project metadata and structure. It has no capability to modify, delete, execute, or move money. The 'scan_depth' parameter controls analysis scope but does not alter the codebase. Classification as Read is appropriate for static code analysis that produces informational output only.

From the tool's definition Tool performs 'Analyze overall project structure' with args for project name and scan depth, returning a 'Project analysis'. It scans and examines code structure without modifying, deleting, or executing code.

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

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

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

analyze_project 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 Tree Sitter — 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.

Go deeper

What does the analyze_project tool do? +

Analyze overall project structure. Args: project: Project name scan_depth: Depth of detailed analysis (higher is slower) ctx: Optional MCP context for progress reporting Returns: Project analysis. It is categorised as a Read tool in the Tree Sitter MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on analyze_project? +

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

What risk level is analyze_project? +

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

Can I rate-limit analyze_project? +

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

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

analyze_project is provided by the Tree Sitter MCP server (wrale/mcp-server-tree-sitter). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Tree Sitter tool call.

Deterministic rules across all 26 Tree Sitter tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

26 Tree Sitter tools catalogued and risk-classified — across an index of 42,500+ 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.