Add or update an item in the recommendation catalogue.
AI agents use upsert_item to create or update resources in NeuronSearchLab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NeuronSearchLab environment.
This tool modifies catalogue data but does not irreversibly delete it (which would be Destructive), does not execute arbitrary code (Execute), does not move money (Financial), and is not merely a read operation (Read). The blast radius is moderate—incorrect catalogue entries could degrade recommendation quality or expose bad data, but the operation is reversible by updating or deleting the item via other means.
From the tool's definition Tool name is 'upsert_item' and description states it can 'Add or update an item in the recommendation catalogue.' Upsert (update-or-insert) is a reversible write operation that creates or modifies data.
Attacks that exploit this kind of access
Add or update an item in the recommendation catalogue. It is categorised as a Write tool in the NeuronSearchLab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the NeuronSearchLab MCP server in PolicyLayer and add a rule for upsert_item: 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 NeuronSearchLab. Nothing to install.
upsert_item 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 upsert_item 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 upsert_item. 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.
upsert_item is provided by the NeuronSearchLab MCP server (neuronsearchlab/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 →