<tool> <purpose>Prepares a codebase for intelligent search by creating a searchable index</purpose> <when_to_use> <scenario>Call this first before searching any new codebase</scenario> <scenario>Required prerequisite for search_codebase</scenario> </when_to_use> <parameters> <parameter name=
AI agents use index_codebase to create or update resources in DeepContext — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DeepContext environment.
This tool creates a new index (a persistent data structure) from codebase files. It is a Write operation — it produces new stored data — but is reversible (the sibling tool 'clear_index' can undo it). It does not execute code or delete data, so Write is the appropriate category. Severity is medium because indexing could process large codebases and store sensitive source code in an index.
From the tool's definition Prepares a codebase for intelligent search by creating a searchable index
Documented attack patterns abuse exactly the kind of access index_codebase gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DeepContext, and nothing reaches the server without passing your rules. This is the rule we recommend for index_codebase:
{
"version": "1",
"default": "deny",
"tools": {
"index_codebase": {
"limits": [
{
"counter": "index_codebase_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}index_codebase 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.
<tool> <purpose>Prepares a codebase for intelligent search by creating a searchable index</purpose> <when_to_use> <scenario>Call this first before searching any new codebase</scenario> <scenario>Required prerequisite for search_codebase</scenario> </when_to_use> <parameters> <parameter name=. It is categorised as a Write tool in the DeepContext MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DeepContext MCP server in PolicyLayer and add a rule for index_codebase: 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 DeepContext. Nothing to install.
index_codebase 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_codebase 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_codebase. 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_codebase is provided by the DeepContext MCP server (wildcard-official/deepcontext-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 DeepContext tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 DeepContext tools catalogued and risk-classified — across an index of 42,500+ MCP servers.