Disable a ranking rule without deleting it. Useful for temporarily pausing rules during debugging or campaigns.
AI agents use disable_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 modifies system configuration by changing the state of ranking rules, which affects how recommendations are generated and delivered. It is Write rather than Destructive because the action is explicitly reversible ('without deleting it'), and the tool description indicates rules can be re-enabled.
From the tool's definition disable_rule: Disable a ranking rule without deleting it. Useful for temporarily pausing rules during campaigns.
Attacks that exploit this kind of access
Disable a ranking rule without deleting it. Useful for temporarily pausing rules during debugging or campaigns. 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 disable_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.
disable_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 disable_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 disable_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.
disable_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 →