Get custom event counts for a website over time. Returns event name, timestamp, and count rows.
AI agents call umami_get_events_series to retrieve information from Umami MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves historical event analytics data from Umami. It has no capability to modify, delete, or execute operations—it only fetches and returns aggregated event metrics. The read-only nature of the server combined with the retrieval-only operation places this firmly in the Read category with low severity.
From the tool's definition Server is described as 'Read-only MCP server' and tool 'Get custom event counts for a website over time. Returns event name, timestamp, and count rows' retrieves analytics data without modification.
Attacks that exploit this kind of access
Get custom event counts for a website over time. Returns event name, timestamp, and count rows. It is categorised as a Read tool in the Umami MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Umami MCP Server MCP server in PolicyLayer and add a rule for umami_get_events_series: 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 Umami MCP Server. Nothing to install.
umami_get_events_series 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 umami_get_events_series 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 umami_get_events_series. 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.
umami_get_events_series is provided by the Umami MCP Server MCP server (mzaxd/umami-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 →