Update an existing ranking rule.
AI agents use update_rule 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 or modifies data reversibly by updating ranking rules. It does not delete data (not Destructive), does not execute arbitrary code (not Execute), does not move money (not Financial), and does not merely retrieve information (not Read). The blast radius is medium because misconfigured ranking rules could affect recommendation quality and user experience, but changes can typically be reverted.
From the tool's definition Tool name 'update_rule' indicates modification of existing data. Description states 'Update an existing ranking rule' - the verb 'update' clearly indicates a write/modification operation.
Attacks that exploit this kind of access
Update an existing ranking rule. 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 update_rule: 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.
update_rule 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 update_rule 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 update_rule. 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.
update_rule 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 →