Compare two items head-to-head by served count, events, clicks, and click-through rate over the same time window.
AI agents call compare_items 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 and analyzes existing data (metrics/analytics) for two items without creating, modifying, or destructively removing any data. It performs a comparison query, which is a read-only operation. No side effects are created beyond returning comparative information.
From the tool's definition Tool compares items by 'served count, events, clicks, and click-through rate' — purely analytical retrieval of metrics with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Compare two items head-to-head by served count, events, clicks, and click-through rate over the same time window. 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 compare_items: 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.
compare_items 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 compare_items 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 compare_items. 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.
compare_items 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 →