agentproxy_session · Novada Proxy MCP: Risk & Policy

WHAT IT DOES

What agentproxy_session does on Novada Proxy

AI agents invoke agentproxy_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.

WHY IT NEEDS A POLICY

Why agentproxy_session needs a policy

This tool executes HTTP requests through residential proxy infrastructure, maintaining session state across requests. It is designed to bypass anti-bot systems and enable login flows and scraping workflows — external operations whose effects depend on the arguments passed.

From the tool's definition 'Fetch a URL with a sticky session', 'bypassing anti-bot systems', 'login flows, paginated scraping, price monitoring', 'same residential IP is used for every call'

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

agentproxy_session Rate-limited

agentproxy_session 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "agentproxy_session": {
      "limits": [
        {
          "counter": "agentproxy_session_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Novada Proxy, so you can run agents against it safely.

FAQ

Questions about agentproxy_session

What does the agentproxy_session tool do? +

Fetch a URL with a sticky session \u2014 the same residential IP is used for every call with the same session_id. Use this for multi-step workflows where IP consistency matters: login flows, paginated scraping, price monitoring. 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.

How do I enforce a policy on agentproxy_session? +

Register the Novada Proxy MCP server in PolicyLayer and add a rule for agentproxy_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.

What risk level is agentproxy_session? +

agentproxy_session is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit agentproxy_session? +

Yes. Add a rate_limit block to the agentproxy_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.

How do I block agentproxy_session completely? +

Set action: deny in the PolicyLayer policy for agentproxy_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.

What MCP server provides agentproxy_session? +

agentproxy_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.