[BETA] Render a JavaScript-heavy page using Novada
AI agents invoke agentproxy_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.
Rendering a JavaScript-heavy page involves executing JS code in a headless browser or similar environment, which constitutes running external operations. While the primary output is a read (page content), the execution of arbitrary JavaScript and the routing through residential IPs to bypass anti-bot systems elevates this beyond a simple read.
From the tool's definition 'Render a JavaScript-heavy page' — executes JavaScript in a browser context via Novada's proxy infrastructure, routing through residential IPs to bypass anti-bot systems
Attacks that exploit this kind of access
[BETA] Render a JavaScript-heavy page using Novada. 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 agentproxy_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.
agentproxy_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 agentproxy_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 agentproxy_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.
agentproxy_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.
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 →