Fetch a URL with sticky-session IP persistence and optional verification. For basic sticky routing without verification, use novada_proxy_fetch with session_id instead.\n\nReuses the same residential IP across calls with the same session_id. Returns structured JSON. Use verify_sticky:true to conf...
AI agents invoke novada_proxy_session 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 executes HTTP requests through residential proxy IPs with session persistence, enabling multi-step operations like login flows and scraping. It actively routes external network requests and can be used to bypass anti-bot systems, making it an Execute-category tool with high severity due to potential misuse for unauthorized scraping, credential stuffing via login flows, or circumventing access controls at…
From the tool's definition Fetch a URL with sticky-session IP persistence and optional verification... Reuses the same residential IP across calls with the same session_id... Multi-step workflows where IP consistency matters: login flows, paginated scraping, price monitoring.
Attacks that exploit this kind of access
Fetch a URL with sticky-session IP persistence and optional verification. For basic sticky routing without verification, use novada_proxy_fetch with session_id instead.\n\nReuses the same residential IP across calls with the same session_id. Returns structured JSON. Use verify_sticky:true to confirm the session held.\n\nWHEN TO USE: Multi-step workflows where IP consistency matters: login flows, paginated scraping, price monitoring.\nNOTE: Sticky sessions are best-effort — infrastructure may not guarantee 100% IP consistency. Use verify_sticky:true to confirm.\nNOTE: verify_sticky:true makes 3 sequential proxy calls and adds ~15-25 seconds. Only use it when you need to confirm IP consistency before a multi-step workflow.\nON FAILURE: If SESSION_STICKINESS_FAILED → regenerate session_id or accept best-effort behavior. 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_session: 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_session 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_session 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_session. 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_session 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 →