Indexes a single file for code context and entities, making it available for vector search. Supports Python, JavaScript, and TypeScript files.
AI agents use index_file to create or update resources in Code Context Manager — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Code Context Manager environment.
Indexing a file creates new data (index entries, vector embeddings) in the system's storage. This is a reversible write operation — the sibling tool 'remove_indexed_file' can undo it. It does not execute code or delete data, so Write is the appropriate category. Severity is medium because misuse could pollute the search index with unintended or malicious content, affecting all subsequent semantic searches.
From the tool's definition 'Indexes a single file for code context and entities, making it available for vector search'
Attacks that exploit this kind of access
Indexes a single file for code context and entities, making it available for vector search. Supports Python, JavaScript, and TypeScript files. It is categorised as a Write tool in the Code Context Manager MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Code Context Manager MCP server in PolicyLayer and add a rule for index_file: 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 Code Context Manager. Nothing to install.
index_file 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_file 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_file. 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_file is provided by the Code Context Manager MCP server (theraaz/code-context-manager-mcp). 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 →