Batch index all documents from a directory into Elasticsearch with AI-enhanced metadata generation and comprehensive file processing
AI agents use batch_index_directory to create or update resources in Agent Knowledge MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent Knowledge MCP environment.
This tool reads files from a directory and writes/creates index entries in Elasticsearch for all of them. It is a bulk write operation that creates or updates many documents at once. The blast radius is high because a misconfigured batch operation could pollute or overwrite large portions of the search index with incorrect metadata or unintended documents.
From the tool's definition Batch index all documents from a directory into Elasticsearch with AI-enhanced metadata generation and comprehensive file processing
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access batch_index_directory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agent Knowledge MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for batch_index_directory:
{
"version": "1",
"default": "deny",
"tools": {
"batch_index_directory": {
"limits": [
{
"counter": "batch_index_directory_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}batch_index_directory 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.
Batch index all documents from a directory into Elasticsearch with AI-enhanced metadata generation and comprehensive file processing. It is categorised as a Write tool in the Agent Knowledge MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agent Knowledge MCP server in PolicyLayer and add a rule for batch_index_directory: 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 Agent Knowledge MCP. Nothing to install.
batch_index_directory 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 batch_index_directory 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 batch_index_directory. 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.
batch_index_directory is provided by the Agent Knowledge MCP server (itshare4u/agentknowledgemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Agent Knowledge MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
27 Agent Knowledge MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.