AI agents call get_website_metrics to retrieve information from Umami Analytics MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool is part of an analytics server designed to 'provide access to website analytics data' and retrieve 'user behavior' and 'website performance' metrics. The 'get_' prefix and alignment with other retrieval-only siblings (get_active_visitors, get_website_stats, get_pageview_series, get_tracking_data) indicates this is a read operation that queries existing analytics data without modification, deletion, or side…
From the tool's definition Tool name 'get_website_metrics' follows the 'get_*' pattern consistent with sibling tools (get_active_visitors, get_pageview_series, get_website_stats, etc.) which are all data retrieval operations.
Documented attack patterns abuse exactly the kind of access get_website_metrics gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Umami Analytics MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_website_metrics:
{
"version": "1",
"default": "deny",
"tools": {
"get_website_metrics": {}
}
}get_website_metrics is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_website_metrics. It is categorised as a Read tool in the Umami Analytics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Umami Analytics MCP Server MCP server in PolicyLayer and add a rule for get_website_metrics: 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 Analytics MCP Server. Nothing to install.
get_website_metrics 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 get_website_metrics 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 get_website_metrics. 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.
get_website_metrics is provided by the Umami Analytics MCP Server MCP server (jakeyshakey/umami_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Umami Analytics MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Umami Analytics MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.