analytics_get_contact_journey
Chronological list of page-view and search events recorded for one identified visitor. Pass either
This record as markdown: /tools/com-getmunin-munin/analytics-get-contact-journey.md
What analytics_get_contact_journey does on Munin
AI agents call analytics_get_contact_journey 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_contact_journey is rated Low
This tool queries and returns historical analytics data about a visitor's journey. It performs data retrieval only, with no side effects, mutations, or external operations. The blast radius is minimal since it accesses read-only analytics records. Categorized as Read with low severity.
From the tool's definition Tool retrieves 'chronological list of page-view and search events' for a visitor—a query operation with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs analytics_get_contact_journey 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_contact_journey, this is the rule to start with:
analytics_get_contact_journey 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_contact_journey call is checked against it from then on.
Questions about analytics_get_contact_journey
Chronological list of page-view and search events recorded for one identified visitor. Pass either. 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_contact_journey: 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_contact_journey 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_contact_journey 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_contact_journey. 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_contact_journey 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