Embed and index documents into Chroma.
AI agents use index_documents to create or update resources in MCP Tooling Lab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Tooling Lab environment.
This tool writes new data (document embeddings and index entries) into the Chroma vector store. It is reversible in principle (indexed documents can be deleted), so it falls under Write rather than Destructive. Misuse could lead to polluted or unauthorized data being indexed into the knowledge base, affecting downstream RAG query results, hence medium severity.
From the tool's definition 'Embed and index documents into Chroma' — creates and stores new embeddings/index entries in the Chroma vector database
Attacks that exploit this kind of access
Embed and index documents into Chroma. It is categorised as a Write tool in the MCP Tooling Lab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Tooling Lab MCP server in PolicyLayer and add a rule for index_documents: 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 MCP Tooling Lab. Nothing to install.
index_documents 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_documents 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_documents. 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_documents is provided by the MCP Tooling Lab MCP server (kaypon/mcp-tooling-lab). 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 →