Critical Risk →

remove_project_tool

Remove a registered project. Args: name: Project name Returns: Success message

How to control remove_project_tool ↓

AI agents call remove_project_tool to permanently remove resources in Tree Sitter — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

This tool irreversibly deletes registered project state from the MCP server's configuration. While not data destruction at the file system level, removing a project registration eliminates all associated metadata and analysis configuration, which cannot be undone through normal tool operations.

From the tool's definition Tool name 'remove_project_tool' and description 'Remove a registered project' indicate deletion of project data without explicit recovery mechanism.

Documented attack patterns abuse exactly the kind of access remove_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 remove_project_tool:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_project_tool"
  ]
}

remove_project_tool disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  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.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the remove_project_tool tool do? +

Remove a registered project. Args: name: Project name Returns: Success message. It is categorised as a Destructive tool in the Tree Sitter MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_project_tool? +

Register the Tree Sitter MCP server in PolicyLayer and add a rule for remove_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.

What risk level is remove_project_tool? +

remove_project_tool is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_project_tool? +

Yes. Add a rate_limit block to the remove_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.

How do I block remove_project_tool completely? +

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

What MCP server provides remove_project_tool? +

remove_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.

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.