analytics_get_views_over_time
Daily view + unique-visitor counts over a recent window. Returns one row per UTC day, ordered oldest → newest, with zero-filled gaps so days with no traffic appear as
This record as markdown: /tools/com-getmunin-munin/analytics-get-views-over-time.md
What analytics_get_views_over_time does on Munin
AI agents call analytics_get_views_over_time to retrieve information from Munin without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why analytics_get_views_over_time is rated Low
This tool purely queries and retrieves historical analytics data (views and visitor counts aggregated by day). It does not create, modify, delete, execute commands, or transfer funds. The zero-filled gaps and ordering are presentation details of a read operation. No destructive, write, execute, or financial capability is present.
From the tool's definition Tool returns 'Daily view + unique-visitor counts' with no side effects described. Action is retrieval ('Returns one row per UTC day') of analytics data.
Attacks that exploit this kind of access
The rule that runs analytics_get_views_over_time safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Munin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For analytics_get_views_over_time, this is the rule to start with:
analytics_get_views_over_time is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Munin, apply this rule, and every analytics_get_views_over_time call is checked against it from then on.
Questions about analytics_get_views_over_time
Daily view + unique-visitor counts over a recent window. Returns one row per UTC day, ordered oldest → newest, with zero-filled gaps so days with no traffic appear as. It is categorised as a Read tool in the Munin MCP Server, which means it retrieves data without modifying state.
Register the Munin MCP server in PolicyLayer and add a rule for analytics_get_views_over_time: 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 Munin. Nothing to install.
analytics_get_views_over_time 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 analytics_get_views_over_time 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 analytics_get_views_over_time. 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.
analytics_get_views_over_time is provided by the Munin MCP server (https://mcp.getmunin.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Munin, and thousands of servers like it.
This server
Across the catalogue