analytics_selfhost_events

Query recent analytics events from self-hosted engine.

Server Yaver yaver-cli
Category Read
Risk class Low
Parameters 30 required

What analytics_selfhost_events does on Yaver

AI agents call analytics_selfhost_events to retrieve information from Yaver without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
last string Time window: 24h, 7d, 30d
event string Event name filter
person_id string Person/user filter

Parameters from the server's own tool schema.

Why analytics_selfhost_events needs a policy

Even though analytics_selfhost_events only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about analytics_selfhost_events

What does the analytics_selfhost_events tool do? +

Query recent analytics events from self-hosted engine. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does analytics_selfhost_events accept? +

analytics_selfhost_events accepts 3 parameters: last, event, person_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on analytics_selfhost_events? +

Register the Yaver MCP server in PolicyLayer and add a rule for analytics_selfhost_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 Yaver. Nothing to install.

What risk level is analytics_selfhost_events? +

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

Can I rate-limit analytics_selfhost_events? +

Yes. Add a rate_limit block to the analytics_selfhost_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 analytics_selfhost_events completely? +

Set action: deny in the PolicyLayer policy for analytics_selfhost_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 analytics_selfhost_events? +

analytics_selfhost_events is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.