add_text_to_index
AI agents use add_text_to_index to create or update resources in ElasticMind-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ElasticMind-MCP environment.
This tool creates or appends new text data to an Elasticsearch index, which is a reversible write operation. While the description is empty, the name and server context make the intent clear. Severity is medium because uncontrolled text ingestion could pollute the knowledge base or introduce misleading information, but the operation itself is reversible via deletion or re-indexing.
From the tool's definition Tool name 'add_text_to_index' combined with server description stating it 'ingest new files, and dynamically update content' indicates this tool modifies indexed data by adding text entries to an Elasticsearch index.
Attacks that exploit this kind of access
add_text_to_index. It is categorised as a Write tool in the ElasticMind-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ElasticMind- MCP server in PolicyLayer and add a rule for add_text_to_index: 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 ElasticMind-MCP. Nothing to install.
add_text_to_index 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 add_text_to_index 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 add_text_to_index. 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.
add_text_to_index is provided by the ElasticMind- MCP server (viratgarg2/elasticmind-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 →