# agent_web_reader

Paid (x402, $0.002 USDC on Base). Fetch any http(s) URL and return clean readable text, title/description/canonical, and outbound links as JSON — the data an agent ingests on each step of a crawl/RAG loop.

Agent View of the PolicyLayer registry record for `agent_web_reader`. HTML page: https://policylayer.com/tools/dev-charliemorrison-agent-web-reader/agent-web-reader

## Facts

- Tool: `agent_web_reader`
- Server: Agent Web Reader (`https://x402.charliemorrison.dev/mcp`) — https://policylayer.com/tools/dev-charliemorrison-agent-web-reader.md
- Homepage: https://github.com/charlie-morrison/x402-agent-data
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 2 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `url` | string | yes | Absolute http(s) URL to fetch and extract (e.g. 'https://example.com/article') |
| `x402_payment` | string | no | Base64 X-PAYMENT header from your x402 wallet (omit to get the payment challenge) |

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

## Why agent_web_reader is rated Low

This tool retrieves and reads web content, returning structured data for consumption. It has no side effects on the target systems or data stores. The financial component (paid service at $0.002 USDC per call) is a cost to the caller, not a financial transaction moving money between parties or committing obligations, so it does not qualify as Financial category.

From the tool's own definition: "Tool description states it 'Fetch[es]...URL and return[s] clean readable text, title/description/canonical, and outbound links as JSON' — a retrieval operation with no modification or deletion of data."

Risk signals: Accepts URL/endpoint input (url)

## Use case

AI agents call agent_web_reader to retrieve information from Agent Web Reader 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 Agent Web Reader:

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

## Other tools on Agent Web Reader (2)

- `crypto_market_signal` — Read — https://policylayer.com/tools/dev-charliemorrison-agent-web-reader/crypto-market-signal.md
- `github_repo_seo_audit` — Read — https://policylayer.com/tools/dev-charliemorrison-agent-web-reader/github-repo-seo-audit.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=dev-charliemorrison-agent-web-reader · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-charliemorrison-agent-web-reader