AI agents call rybbit_get_journeys to retrieve information from Rybbit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely queries and retrieves analytics data about user navigation patterns. It has no side effects, does not modify or delete data, and does not execute code or trigger external operations. It is a straightforward read operation on analytics metrics, consistent with other Read-category tools like rybbit_get_errors and rybbit_get_funnel_step_sessions on the same server.
From the tool's definition Tool retrieves user journey and navigation path data ('Get user journey analysis', 'Shows sequences of pages users visit'). No modification, deletion, or execution capabilities described.
Attacks that exploit this kind of access
Get user journey (flow) analysis showing the most common navigation paths through the site. Shows sequences of pages users visit and how many sessions follow each path. It is categorised as a Read tool in the Rybbit MCP Server, which means it retrieves data without modifying state.
Register the Rybbit MCP server in PolicyLayer and add a rule for rybbit_get_journeys: 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 Rybbit. Nothing to install.
rybbit_get_journeys 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 rybbit_get_journeys 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 rybbit_get_journeys. 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.
rybbit_get_journeys is provided by the Rybbit MCP server (nks-hub/rybbit-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 →