List all registered projects. Returns: List of project information
AI agents call list_projects_tool 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.
This tool performs a simple enumeration/listing operation. It retrieves metadata about registered projects without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal—an AI agent could only learn which projects exist in the system, which is low-risk information disclosure.
From the tool's definition Tool name 'list_projects_tool' and description 'List all registered projects' clearly indicate a retrieval operation with no side effects. The return value is 'List of project information', confirming it queries and returns data without modification.
Documented attack patterns abuse exactly the kind of access list_projects_tool 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 list_projects_tool:
{
"version": "1",
"default": "deny",
"tools": {
"list_projects_tool": {}
}
}list_projects_tool 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.
List all registered projects. Returns: List of project information. It is categorised as a Read tool in the Tree Sitter MCP Server, which means it retrieves data without modifying state.
Register the Tree Sitter MCP server in PolicyLayer and add a rule for list_projects_tool: 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.
list_projects_tool 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 list_projects_tool 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 list_projects_tool. 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.
list_projects_tool 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.
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.