Create a new recommendation context (feed).
AI agents use create_context 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 creates new data structures (recommendation contexts/feeds) within the NeuronSearchLab system. Creation is a Write-category action because it modifies state by adding new records, but the operation is reversible (the context can be deleted or modified later). It does not execute arbitrary code, delete data irreversibly, or transfer funds.
From the tool's definition Tool description explicitly states 'Create a new recommendation context (feed)' — the verb 'create' and the action of establishing a new feed object are reversible write operations.
Attacks that exploit this kind of access
Create a new recommendation context (feed). 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 create_context: 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.
create_context 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 create_context 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 create_context. 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.
create_context 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 →