navigate
Navega a una URL. Devuelve title + URL final + status_code.
This record as markdown: /tools/4bis-relay-showcase/navigate.md
What navigate does on 4bis Relay Showcase
AI agents invoke navigate to trigger actions in 4bis Relay Showcase. 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.
Why navigate is rated High
Tool navigates to arbitrary URLs, triggering external HTTP requests whose effects depend on target.
From the tool's definition Navega a una URL (navigate to URL); external network request with side effects.
Attacks that exploit this kind of access
The rule that runs navigate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 4bis Relay Showcase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For navigate, this is the rule to start with:
navigate stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 4bis Relay Showcase, apply this rule, and every navigate call is checked against it from then on.
Questions about navigate
Navega a una URL. Devuelve title + URL final + status_code. It is categorised as a Execute tool in the 4bis Relay Showcase MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the 4bis Relay Showcase MCP server in PolicyLayer and add a rule for navigate: 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 4bis Relay Showcase. Nothing to install.
navigate 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 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. 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 is provided by the 4bis Relay Showcase MCP server (FourBis/4bis.relay-showcase). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 4bis Relay Showcase, and thousands of servers like it.
Across the catalogue