Render a JavaScript-heavy page with real Chromium [BETA]. Returns structured JSON with ok, data.content. Requires NOVADA_BROWSER_WS env var.\n\nWHEN TO USE: SPAs, React/Vue apps, infinite scroll, pages that require JS to load content.\nUSE novada_proxy_fetch INSTEAD FOR: Static HTML pages — it is...
AI agents invoke novada_proxy_render to trigger actions in Novada Proxy. 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 launches and controls a real Chromium browser instance to render pages, which involves executing JavaScript code from external pages. Combined with the server's capability to route through residential IPs to bypass anti-bot systems, misuse could involve executing malicious JS, fingerprinting evasion, or scraping at scale.
From the tool's definition 'Render a JavaScript-heavy page with real Chromium' — executes a real browser (Chromium) to render pages, running arbitrary JavaScript in the process
Attacks that exploit this kind of access
Render a JavaScript-heavy page with real Chromium [BETA]. Returns structured JSON with ok, data.content. Requires NOVADA_BROWSER_WS env var.\n\nWHEN TO USE: SPAs, React/Vue apps, infinite scroll, pages that require JS to load content.\nUSE novada_proxy_fetch INSTEAD FOR: Static HTML pages — it is 3-5x faster.\nON FAILURE: If error.code is TIMEOUT → increase timeout. If PROVIDER_NOT_CONFIGURED → set NOVADA_BROWSER_WS. It is categorised as a Execute tool in the Novada Proxy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Novada Proxy MCP server in PolicyLayer and add a rule for novada_proxy_render: 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 Novada Proxy. Nothing to install.
novada_proxy_render 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 novada_proxy_render 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 novada_proxy_render. 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.
novada_proxy_render is provided by the Novada Proxy MCP server (novadalabs/novada-proxy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
novada_proxy_render is one line of Novada Proxy's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →