# foura_single

Send one HTTP request and return the response. Fastest of the four tools (typically 200ms-2s). Use for static pages, JSON APIs, server-rendered HTML. Set unblocker:true if the target has wire-level anti-bot protection. Switch to foura_proxy if you get blocked - status 403, status 429, captcha page, OR response carries x-vercel-mitigated: challenge / cf-mitigated: challenge headers, OR body title matches Vercel Security Checkpoint / Just a moment / Attention Required / We're verifying your browser. For these tier-1 WAF challenges call foura_proxy with maxTries:25-30 (the default 5 is sized for lightly-blocked sites). On success, chain the returned proxy ID into foura_browser.proxy if the page also needs JavaScript to render.

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

## Facts

- Tool: `foura_single`
- 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: Read (Low risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 12 (2 required)
- Recommended policy verdict: Allowed

## Parameters

| 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 | no | Request body. Strings sent as-is; objects auto-serialized to JSON. Example: {"query": "hello"} for POST APIs. |
| `proxy` | string | no | Optional proxy. Two forms: (1) URL `http://host:port` or `socks5://host:port`; (2) base36 ID from foura_proxy (e.g. `4DZ3VE`) - same exit IP. For rotation, use |
| `method` | string | yes | HTTP method (GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS, or any WebDAV verb like PROPFIND/MKCOL) |
| `headers` | array | no | Custom HTTP headers as [name, value] tuples. Example: [["Accept", "application/json"], ["Referer", "https://google.com/"]] |
| `validate` | object | no | Post-fetch response validation. When the response fails these checks the tool returns an error envelope. |
| `unblocker` | boolean | no | Inject realistic browser headers (User-Agent, Sec-Ch-Ua, Accept-Encoding, …) and make the request look like it's coming from a real browser at the wire level. D |
| `timeout_ms` | integer | no | Overall request timeout in ms (max 120000, default 15000) |
| `tryJsonData` | boolean | no | If true, attempt JSON.parse on the response body. On success, `data` is the parsed value (typically object or array). On parse failure, `data` silently stays as |
| `returnBuffer` | boolean | no | Return raw bytes as a serialized Buffer JSON shape (`{type:"Buffer", data:[byte, ...]}`, bytes 0-255) instead of decoded string. Use for binary responses (image |
| `offload_large` | boolean | no | 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 |
| `followRedirects` | integer | no | Max number of redirects to follow (0-20). Omit to disable redirect following. |

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_single",
    "arguments": {
      "url": "<url>",
      "method": "<method>"
    }
  }
}
```

## Why foura_single is rated Low

This tool fetches web pages and API responses via HTTP requests, which is a read/retrieval operation. It has no write or destructive side effects on its own. The medium severity reflects the potential for misuse in scraping sensitive data, bypassing anti-bot protections, or accessing restricted content behind WAFs/CAPTCHAs.

From the tool's own definition: "Send one HTTP request and return the response. Use for static pages, JSON APIs, server-rendered HTML."

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

## Use case

AI agents call foura_single 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.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "foura_single": {}
  }
}
```

## Other tools on Mcp (3)

- `foura_proxy` — Execute — https://policylayer.com/tools/ai-foura-mcp/foura-proxy.md
- `foura_auto` — Read — https://policylayer.com/tools/ai-foura-mcp/foura-auto.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