Per-day timeline of specific events. Use to detect cutover dates — the day a group STOPS (or starts) firing an event. event_names is REQUIRED to bound output. Counts are bucketed by calendar day (UTC). Ranges > 31 days auto-split. Inputs: event_names: REQUIRED list, e.g. [
AI agents call vexo_event_timeline 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 analytics data from the Vexo Export API to analyze event timelines and detect trends. It retrieves information about when events occur but does not create, modify, delete, or execute any operations. The required input (event_names) bounds the query scope.
From the tool's definition Tool retrieves a 'per-day timeline of specific events' and 'counts are bucketed by calendar day'. The description indicates querying and analysis of event data without any mention of modification, deletion, or execution of code.
Attacks that exploit this kind of access
Per-day timeline of specific events. Use to detect cutover dates — the day a group STOPS (or starts) firing an event. event_names is REQUIRED to bound output. Counts are bucketed by calendar day (UTC). Ranges > 31 days auto-split. Inputs: event_names: REQUIRED list, e.g. [. 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_event_timeline: 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_event_timeline 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_event_timeline 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_event_timeline. 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_event_timeline 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 →