This record as markdown: /tools/seac-25-kali-security-mcp/browser-navigate.md
What browser_navigate does on Kali Security MCP
AI agents invoke browser_navigate to trigger actions in Kali Security MCP. 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 browser_navigate is rated High
Browser navigation is an Execute-class action because it triggers external operations (HTTP requests, JavaScript execution, page rendering) and can interact with arbitrary websites or internal services. The severity is high because an AI agent could be manipulated to navigate to malicious sites, exfiltrate data via navigation patterns, or trigger unintended side effects.
From the tool's definition Tool description states it 'navigates to a new page in an existing session' (browser_navigate). This performs browser automation actions that trigger external operations (page loads, script execution, potential data fetching) whose effects depend on the…
Attacks that exploit this kind of access
The rule that runs browser_navigate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Kali Security MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_navigate, this is the rule to start with:
browser_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 Kali Security MCP, apply this rule, and every browser_navigate call is checked against it from then on.
Questions about browser_navigate
在已有会话中导航到新页面. It is categorised as a Execute tool in the Kali Security MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali Security MCP server in PolicyLayer and add a rule for browser_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 Kali Security MCP. Nothing to install.
browser_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 browser_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 browser_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.
browser_navigate is provided by the Kali Security MCP server (seac-25/kali-security-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Kali Security, and thousands of servers like it.
Across the catalogue