Upsert documents into Lucene index.
AI agents use lucene_upsert to create or update resources in Mcp Lucene — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Lucene environment.
This tool creates or modifies documents in a Lucene search index. Upsert operations are reversible writes—documents can be updated or re-indexed. While it modifies data, it does not permanently delete or destroy information. Severity is medium because misuse could corrupt search indices or introduce malicious data into indexed content, but the operation itself is not irreversible.
From the tool's definition Tool is named 'lucene_upsert' and described as 'Upsert documents into Lucene index.' Upsert is a reversible write operation (insert or update).
Attacks that exploit this kind of access
Upsert documents into Lucene index. It is categorised as a Write tool in the Mcp Lucene MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Lucene MCP server in PolicyLayer and add a rule for lucene_upsert: 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 Lucene. Nothing to install.
lucene_upsert 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 lucene_upsert 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 lucene_upsert. 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.
lucene_upsert is provided by the Mcp Lucene MCP server (vivekkumarneu/mcp-lucene-server). 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 →