AI agents call get_session_ids 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.
Session IDs are sensitive identifiers that could be used to track or identify individual users. While the tool itself only retrieves existing data (no side effects), the sensitivity of session identifiers and potential for misuse in privacy violations justifies 'high' severity. The empty description reduces confidence slightly, but the naming pattern and server context strongly indicate this is a read operation.
From the tool's definition Tool name 'get_session_ids' indicates retrieval of session identifiers. Sibling tools are all 'get_*' prefixed (get_active_visitors, get_tracking_data, get_website_metrics, get_websites), consistent with read-only data retrieval.
Documented attack patterns abuse exactly the kind of access get_session_ids 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_session_ids:
{
"version": "1",
"default": "deny",
"tools": {
"get_session_ids": {}
}
}get_session_ids 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_session_ids. 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_session_ids: 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_session_ids 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_session_ids 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_session_ids. 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_session_ids 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.