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

Agent View of the PolicyLayer registry record for `foura_proxy`. HTML page: https://policylayer.com/tools/ai-foura-mcp/foura-proxy

## Facts

- Tool: `foura_proxy`
- Server: Mcp (`@fouradata/mcp`) — https://policylayer.com/tools/ai-foura-mcp.md
- Install: `npx -y @fouradata/mcp`
- Homepage: https://github.com/fouradata/mcp
- Risk category: Execute (High risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 5 (1 required)
- Recommended policy verdict: Rate-limited

## Parameters

| 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 | no | 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 | no | Overall timeout across all rotation attempts in ms (default 45000, max 120000). Must be positive. |
| `ignoreProxies` | array | no | Encoded proxy IDs (base36 strings like "4DZ3VE") OR proxy URLs to exclude from rotation. Both forms are accepted. |
| `offload_large` | boolean | no | 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.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "foura_proxy",
    "arguments": {
      "request": {}
    }
  }
}
```

## 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 own definition: "Route an HTTP request through FourA's proxy pool with automatic retry across multiple proxies... past anti-bot defenses"

Risk signals: Accepts URL/endpoint input (request.url) · High parameter count (28 properties)

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "foura_proxy": {
      "limits": [
        {
          "counter": "foura_proxy_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Mcp (3)

- `foura_auto` — Read — https://policylayer.com/tools/ai-foura-mcp/foura-auto.md
- `foura_single` — Read — https://policylayer.com/tools/ai-foura-mcp/foura-single.md
- `foura_browser` — Write — https://policylayer.com/tools/ai-foura-mcp/foura-browser.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=ai-foura-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/ai-foura-mcp