foura_proxy
Route an HTTP request through FourA's proxy pool with automatic retry across multiple proxies. Per-host proxy rating picks proxies most likely to succeed for the target. Use when foura_single returns 403, captcha, or geo-blocked content. Typical latency 1-5s. The response includes the encoded pro...
This record as markdown: /tools/ai-foura-mcp/foura-proxy.md
What foura_proxy does on Mcp
AI agents invoke foura_proxy to trigger actions in Mcp. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
request | object | Yes | The inner HTTP request to send through each proxy attempt. Validation rules here determine when a proxy is treated as failed and retried. |
maxTries | integer | — | Maximum proxy rotation attempts before giving up (default 5, max 90). Default 5 is sized for lightly-blocked sites. Raise to 25-30 for tier-1 WAF challenges (Ve |
timeout_ms | integer | — | Overall timeout across all rotation attempts in ms (default 45000, max 120000). Must be positive. |
ignoreProxies | array | — | Encoded proxy IDs (base36 strings like "4DZ3VE") OR proxy URLs to exclude from rotation. Both forms are accepted. |
offload_large | boolean | — | If true, response bodies >= 50KB are written to disk and returned as a resource_link instead of inlined. Default false. |
Parameters from the server's own tool schema.
Why foura_proxy is rated High
This tool triggers external HTTP requests routed through proxy infrastructure, executing network operations whose effects depend on arguments (target URL, proxy selection, retry logic). It actively fetches content by routing through proxy pools and bypassing anti-bot defenses, which is an external operation execution rather than a simple read.
From the tool's definition Route an HTTP request through FourA's proxy pool with automatic retry across multiple proxies... past anti-bot defenses
Risk signalsAccepts URL/endpoint input (request.url) · High parameter count (28 properties)
Attacks that exploit this kind of access
The rule that runs foura_proxy 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_proxy, this is the rule to start with:
foura_proxy 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every foura_proxy call is checked against it from then on.
Questions about foura_proxy
Route an HTTP request through FourA's proxy pool with automatic retry across multiple proxies. Per-host proxy rating picks proxies most likely to succeed for the target. Use when foura_single returns 403, captcha, or geo-blocked content. Typical latency 1-5s. The response includes the encoded proxy ID that succeeded ('proxy' field) - reuse it in foura_single.proxy or foura_browser.proxy to pin follow-up requests to the same exit IP, or pass it in ignoreProxies to skip this exit on the next rotation. Escalate to foura_browser if all proxies fail or the page needs JavaScript rendering. When the trigger is a tier-1 WAF challenge (Vercel Security Checkpoint, Cloudflare 'Just a moment', Akamai Bot Manager), set maxTries to 25-30 - the default 5 will usually be too low for these targets. Distinguish from country / ASN allowlist denials (country-licensed bookmakers, government sites): there rotation never helps regardless of maxTries - after ~30 failed attempts on the same block, stop climbing and pivot strategy instead. It is categorised as a Execute tool in the Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
foura_proxy accepts 5 parameters: request, maxTries, timeout_ms, ignoreProxies, offload_large. Required: request. 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_proxy: 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_proxy 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 foura_proxy 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_proxy. 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_proxy 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