Register a project directory for code exploration. Args: path: Path to the project directory name: Optional name for the project (defaults to directory name) description: Optional description of the project Returns: Project information
AI agents use register_project_tool to create or update resources in Tree Sitter — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tree Sitter environment.
This tool creates or modifies project metadata in the server's internal state (registering a project directory). This is a reversible write operation with no destructive consequences—projects can be re-registered or unregistered. It has no ability to delete data, execute code, or cause financial impact.
From the tool's definition Tool registers/creates a project configuration by accepting path, name, and optional description parameters and returns project information. The verb 'register' indicates a write operation that creates or modifies configuration state.
Documented attack patterns abuse exactly the kind of access register_project_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 register_project_tool:
{
"version": "1",
"default": "deny",
"tools": {
"register_project_tool": {
"limits": [
{
"counter": "register_project_tool_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}register_project_tool stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Register a project directory for code exploration. Args: path: Path to the project directory name: Optional name for the project (defaults to directory name) description: Optional description of the project Returns: Project information. It is categorised as a Write tool in the Tree Sitter MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tree Sitter MCP server in PolicyLayer and add a rule for register_project_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.
register_project_tool is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the register_project_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 register_project_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.
register_project_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.