foura_auto
Give a URL, get the content back. The default first choice for any page when you just want the data and don't want to decide how to fetch it. Internally it walks a cost-aware ladder - a fast direct request first, then a rotating proxy, then a full browser session - escalating only as far as the t...
This record as markdown: /tools/ai-foura-mcp/foura-auto.md
What foura_auto does on Mcp
AI agents call foura_auto to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Target URL. Public hosts only - private/reserved ranges (RFC 1918 10/8, 172.16/12, 192.168/16, loopback 127/8, link-local, IPv6 ULA fc00::/7, IPv6 loopback ::1, |
data | object | — | Request body for non-GET methods. Strings sent as-is; objects auto-serialized to JSON. |
method | string | — | HTTP method for the target request (default GET). |
headers | array | — | Custom HTTP headers to send to the TARGET, as [name, value] tuples. Example: [["Accept", "application/json"], ["Authorization", "Bearer ..."]] |
validate | object | — | Post-fetch response validation. When the response fails these checks foura_auto returns an error envelope. |
forceProxy | boolean | — | Always reach the target through a rotating proxy, never from FourA's own egress. Default true (the target never sees FourA's origin IP). Send false to allow the |
timeout_ms | integer | — | Total time budget in ms for the WHOLE operation - auto fires several internal attempts and they must all fit inside this. Default 120000, max 180000. Auto porti |
ignoreProxies | array | — | Exits to AVOID - base36 proxy ids (like "4DZ3VE") or proxy URLs. Auto skips a warm session on one of these and tells its internal proxy search to avoid them too |
offload_large | boolean | — | If true, response bodies >= 50KB are written to disk and returned as a resource_link instead of inlined. Saves token context but requires a client that supports |
returnSession | boolean | — | Return the {proxy, cookies, userAgent} session triple of the winning session so you can replay it through foura_single / foura_proxy later. Default true. Send f |
followRedirects | integer | — | Follow up to N redirects on the cheap (direct / proxy) rungs so a 301/302 lands on the real content instead of being returned as-is. Default 5; 0 = don't follow |
Parameters from the server's own tool schema.
Why foura_auto is rated Low
While web scraping via proxy or automated browser can raise ethical and legal concerns (terms of service violations, potential for reconnaissance on restricted sites), the tool's core function is data retrieval with no side effects on the target or agent's own systems.
From the tool's definition The tool is described as 'Give a URL, get the content back' and is explicitly positioned as 'the default first choice for any page when you just want the data'. It fetches and returns page content without modifying or deleting data.
Risk signalsAccepts URL/endpoint input (url) · High parameter count (20 properties)
Attacks that exploit this kind of access
The rule that runs foura_auto safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For foura_auto, this is the rule to start with:
foura_auto is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every foura_auto call is checked against it from then on.
Questions about foura_auto
Give a URL, get the content back. The default first choice for any page when you just want the data and don't want to decide how to fetch it. Internally it walks a cost-aware ladder - a fast direct request first, then a rotating proxy, then a full browser session - escalating only as far as the target forces it, solving common bot challenges (Cloudflare, and similar) on the way, and cheaply replaying a warm session on repeat calls to the same host. It learns the right settings per host on its own, so there are no maxTries / pool / retry knobs to tune. Pass validate (a substring the real page must contain) on protected targets so it can tell a real page from a challenge page. The response includes a meta trace (which rung delivered, credits spent) and, by default, the winning session ({proxy, cookies, userAgent}) so you can replay it through foura_single / foura_proxy afterwards. Use one of the lower-level tools instead only when you need explicit control: foura_single for a specific raw HTTP request, foura_proxy to drive the rotation/exit yourself, foura_browser for a scripted browser session. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
foura_auto accepts 11 parameters: url, data, method, headers, validate, forceProxy, timeout_ms, ignoreProxies, offload_large, returnSession, followRedirects. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for foura_auto: 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 Mcp. Nothing to install.
foura_auto is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the foura_auto 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 foura_auto. 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.
foura_auto is provided by the MCP server (@fouradata/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue