AI agents call vexo_overview 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.
The vexo_overview tool queries analytics data (event activity) within a date window and returns a summary view. It performs no data modification, deletion, or external operations. It is purely a read operation that retrieves information from the Vexo Export API for analytical purposes. The low severity reflects minimal blast radius—misuse would only expose analytics data already available to users with API access.
From the tool's definition Tool provides a 'high-level breakdown of activity' and is described as a 'good first call to understand an app'.
Attacks that exploit this kind of access
High-level breakdown of activity in a date window. Good first call to understand an app. 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_overview: 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_overview 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_overview 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_overview. 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_overview 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 →