vexo_get_recent_events

Forensic dive into one entity

Server Vexo kishanssg/vexo-mcp
Category Read
Risk class Low
Parameters 00 required

What vexo_get_recent_events does on Vexo

AI agents call vexo_get_recent_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.

Why vexo_get_recent_events needs a policy

This tool queries and retrieves recent event data for forensic analysis purposes. It has no side effects—it does not create, modify, delete, or execute operations. The blast radius of misuse is minimal; an attacker would gain visibility into analytics data but could not alter system state or cause irreversible damage. Classification as Read is appropriate.

From the tool's definition Tool performs a 'forensic dive' into event data from the Vexo Export API, which is a read-only retrieval operation.

Questions about vexo_get_recent_events

What does the vexo_get_recent_events tool do? +

Forensic dive into one entity. It is categorised as a Read tool in the Vexo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on vexo_get_recent_events? +

Register the Vexo MCP server in PolicyLayer and add a rule for vexo_get_recent_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.

What risk level is vexo_get_recent_events? +

vexo_get_recent_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit vexo_get_recent_events? +

Yes. Add a rate_limit block to the vexo_get_recent_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.

How do I block vexo_get_recent_events completely? +

Set action: deny in the PolicyLayer policy for vexo_get_recent_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.

What MCP server provides vexo_get_recent_events? +

vexo_get_recent_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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.