Trigger a full or incremental index scan of a project. Persists configuration and starts the file watcher. Reads tsconfig.json from root_dir automatically to resolve TypeScript path aliases (@scope/... imports). Override with tsconfig_path if your tsconfig is elsewhere.
AI agents use index_project to create or update resources in Knocoph — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Knocoph environment.
This tool writes data to the SQLite knowledge graph by indexing the project and persisting configuration. It also starts a file watcher, which is an ongoing external process. The primary effect is creating/updating persisted data in the database, which is reversible in nature (re-indexing would overwrite). No code execution, deletion, or financial action is involved.
From the tool's definition Trigger a full or incremental index scan of a project. Persists configuration and starts the file watcher.
Attacks that exploit this kind of access
Trigger a full or incremental index scan of a project. Persists configuration and starts the file watcher. Reads tsconfig.json from root_dir automatically to resolve TypeScript path aliases (@scope/... imports). Override with tsconfig_path if your tsconfig is elsewhere. It is categorised as a Write tool in the Knocoph MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Knocoph MCP server in PolicyLayer and add a rule for index_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 Knocoph. Nothing to install.
index_project 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 index_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.
Set action: deny in the PolicyLayer policy for index_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.
index_project is provided by the Knocoph MCP server (jagonzalr/knocoph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →