Discover the event-name vocabulary in a date window (schema discovery). Scans ALL Vexo events in [start_date, end_date] and returns the top 50 event names by frequency. Use this FIRST when you don
AI agents call vexo_get_event_names to retrieve information from Vexo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves analytical data (event names and their frequencies) from a Vexo analytics database within a specified date range. It has no side effects, does not execute code or commands, does not modify or delete data, and does not involve financial transactions.
From the tool's definition Tool description states it 'Discover[s] the event-name vocabulary' and 'returns the top 50 event names by frequency.' The verb 'discover,' 'scan,' and 'returns' indicate read-only data retrieval with no modification or deletion.
Attacks that exploit this kind of access
Discover the event-name vocabulary in a date window (schema discovery). Scans ALL Vexo events in [start_date, end_date] and returns the top 50 event names by frequency. Use this FIRST when you don. It is categorised as a Read tool in the Vexo MCP Server, which means it retrieves data without modifying state.
Register the Vexo MCP server in PolicyLayer and add a rule for vexo_get_event_names: 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 Vexo. Nothing to install.
vexo_get_event_names 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 vexo_get_event_names 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 vexo_get_event_names. 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.
vexo_get_event_names is provided by the Vexo MCP server (kishanssg/vexo-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 →