AI agents invoke navigate_to_journey to trigger actions in Blop. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes browser navigation to a specific URL derived from journey context. Browser navigation is an external operation whose effects depend on the URL argument and the state of the target system. While not inherently destructive or financial, it triggers code execution in a browser environment and could perform unintended actions if the URL or journey context is compromised.
From the tool's definition Tool description states 'Open a recorded journey's entry URL' which triggers browser navigation/execution. The server context describes 'turns browser execution into auditable go/no-go decisions,' confirming this tool performs browser actions.
Attacks that exploit this kind of access
Open a recorded journey's entry URL (flow_id == journey_id). It is categorised as a Execute tool in the Blop MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Blop MCP server in PolicyLayer and add a rule for navigate_to_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 Blop. Nothing to install.
navigate_to_journey is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the navigate_to_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 navigate_to_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.
navigate_to_journey is provided by the Blop MCP server (n2400813g/blop-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 →