Navigate to a URL. Waits for page load. Injects stealth scripts.
AI agents invoke crow_browser_navigate to trigger actions in Crow. 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.
While superficially a navigation action, the tool goes beyond passive retrieval: it waits for page load (executing remote code) and actively injects stealth scripts into the browser context. This is an Execute-category action because it runs code (both remote page scripts and injected stealth code) with side effects determined by the URL and injection payload.
From the tool's definition Tool performs browser navigation with page load execution and injects stealth scripts ('Navigate to a URL. Waits for page load. Injects stealth scripts.'). This triggers external operations whose effects depend on the URL argument and injected code behavior.
Documented attack patterns abuse exactly the kind of access crow_browser_navigate gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crow_browser_navigate:
{
"version": "1",
"default": "deny",
"tools": {
"crow_browser_navigate": {
"limits": [
{
"counter": "crow_browser_navigate_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} crow_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.
Free to start. No card required.
Navigate to a URL. Waits for page load. Injects stealth scripts. It is categorised as a Execute tool in the Crow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Crow MCP server in PolicyLayer and add a rule for crow_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 Crow. Nothing to install.
crow_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 crow_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 crow_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.
crow_browser_navigate is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.