List all configured event types (click, view, purchase, etc.) for the team.
AI agents call list_event_types 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 displays a list of pre-configured event types used by the recommendation engine. It performs data retrieval only, with no capability to modify, delete, or execute actions. The blast radius of misuse is minimal—an agent could only gain visibility into what event types exist in the system. There are no destructive, financial, or code execution implications.
From the tool's definition Tool name 'list_event_types' and description 'List all configured event types' indicate a retrieval operation with no side effects. The verb 'list' is a standard read operation that queries existing data.
Attacks that exploit this kind of access
List all configured event types (click, view, purchase, etc.) for the team. 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 list_event_types: 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.
list_event_types 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 list_event_types 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 list_event_types. 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.
list_event_types 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 →