# clear_project_index

Clear the index for a project (useful for corruption recovery or settings changes). The project will need to be re-indexed after clearing.

Agent View of the PolicyLayer registry record for `clear_project_index`. HTML page: https://policylayer.com/tools/0215andrewfeng-ace-mcp/clear-project-index

## Facts

- Tool: `clear_project_index`
- Server: ACE-MCP (`0215andrewfeng/ace-mcp`) — https://policylayer.com/tools/0215andrewfeng-ace-mcp.md
- Homepage: https://github.com/0215AndrewFeng/ACE-MCP
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "clear_project_index",
    "arguments": {}
  }
}
```

## Why clear_project_index is rated Critical

An AI agent that decides to call clear_project_index doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from ACE-MCP is gone. There is no undo for destructive operations.

## Use case

AI agents call clear_project_index to permanently remove resources in ACE-MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches ACE-MCP:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear_project_index"
  ]
}
```

## Other tools on ACE-MCP (16)

- `warm_index` — Execute — https://policylayer.com/tools/0215andrewfeng-ace-mcp/warm-index.md
- `ask_codebase` — Read — https://policylayer.com/tools/0215andrewfeng-ace-mcp/ask-codebase.md
- `cache_stats` — Read — https://policylayer.com/tools/0215andrewfeng-ace-mcp/cache-stats.md
- `evaluate_search_quality` — Read — https://policylayer.com/tools/0215andrewfeng-ace-mcp/evaluate-search-quality.md
- `find_callees` — Read — https://policylayer.com/tools/0215andrewfeng-ace-mcp/find-callees.md
- `find_callers` — Read — https://policylayer.com/tools/0215andrewfeng-ace-mcp/find-callers.md
- `find_definition` — Read — https://policylayer.com/tools/0215andrewfeng-ace-mcp/find-definition.md
- `find_references` — Read — https://policylayer.com/tools/0215andrewfeng-ace-mcp/find-references.md
- `get_file_snippet` — Read — https://policylayer.com/tools/0215andrewfeng-ace-mcp/get-file-snippet.md
- `get_summary` — Read — https://policylayer.com/tools/0215andrewfeng-ace-mcp/get-summary.md
- `index_project` — Read — https://policylayer.com/tools/0215andrewfeng-ace-mcp/index-project.md
- `list_symbols` — Read — https://policylayer.com/tools/0215andrewfeng-ace-mcp/list-symbols.md
- `project_stats` — Read — https://policylayer.com/tools/0215andrewfeng-ace-mcp/project-stats.md
- `search_context` — Read — https://policylayer.com/tools/0215andrewfeng-ace-mcp/search-context.md
- `generate_summary` — Write — https://policylayer.com/tools/0215andrewfeng-ace-mcp/generate-summary.md
- `resolve_projects` — Write — https://policylayer.com/tools/0215andrewfeng-ace-mcp/resolve-projects.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=0215andrewfeng-ace-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0215andrewfeng-ace-mcp