Fetch the next auto-generated recommendation section for a user.
AI agents call get_auto_recommendations to retrieve information from NeuronSearchLab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves pre-generated recommendation data for a user. It is a query/fetch operation that does not create, modify, delete, or execute code. The verb 'fetch' and the passive construction 'auto-generated recommendation' confirm this is a read-only data retrieval.
From the tool's definition Tool name 'get_auto_recommendations' and description 'Fetch the next auto-generated recommendation section for a user' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Fetch the next auto-generated recommendation section for a user. It is categorised as a Read tool in the NeuronSearchLab MCP Server, which means it retrieves data without modifying state.
Register the NeuronSearchLab MCP server in PolicyLayer and add a rule for get_auto_recommendations: 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.
get_auto_recommendations is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_auto_recommendations 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 get_auto_recommendations. 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.
get_auto_recommendations 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 →