AI agents call vexo_count_events 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 performs data aggregation and retrieval from the Vexo Export API. It queries and counts events over time periods without creating, modifying, deleting, or executing any operations. The automatic deduplication and range-splitting are internal processing logic that does not alter underlying data.
From the tool's definition Tool description states it 'Aggregate event counts over a date range, optionally grouped by a dimension' and mentions comparing cohorts. The verbs are 'aggregate' and 'count' with no mention of modification, deletion, or execution.
Attacks that exploit this kind of access
Aggregate event counts over a date range, optionally grouped by a dimension. The workhorse for cohort comparison. Ranges > 31 days are split & merged automatically (deduped by event id). A. 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_count_events: 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_count_events 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_count_events 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_count_events. 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_count_events 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 →