# fetch_page

Fetches an allowlisted public page as markdown/text: published blog posts (/blog/:slug), static pages (e.g. /agents, /api-docs, /about), and the agent discovery doc (/llms.txt).

Agent View of the PolicyLayer registry record for `fetch_page`. HTML page: https://policylayer.com/tools/com-foliofact-foliofact/fetch-page

## Facts

- Tool: `fetch_page`
- Server: FolioFact (`https://foliofact.com/mcp`) — https://policylayer.com/tools/com-foliofact-foliofact.md
- Homepage: https://github.com/https://foliofact.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: yes
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `path` | string | yes | Public path, e.g. /blog/how-to-read-a-13f-without-overreading-it, /agents, or /llms.txt. |

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": "fetch_page",
    "arguments": {
      "path": "<path>"
    }
  }
}
```

## Why fetch_page is rated Low

Even though fetch_page only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signals: Accepts file system path (path)

## Use case

AI agents call fetch_page to retrieve information from FolioFact 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 FolioFact:

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

## Other tools on FolioFact (12)

- `compare_stocks` — Read — https://policylayer.com/tools/com-foliofact-foliofact/compare-stocks.md
- `fund_history` — Read — https://policylayer.com/tools/com-foliofact-foliofact/fund-history.md
- `fund_holdings` — Read — https://policylayer.com/tools/com-foliofact-foliofact/fund-holdings.md
- `get_fund` — Read — https://policylayer.com/tools/com-foliofact-foliofact/get-fund.md
- `get_investor` — Read — https://policylayer.com/tools/com-foliofact-foliofact/get-investor.md
- `get_stock` — Read — https://policylayer.com/tools/com-foliofact-foliofact/get-stock.md
- `insider_feed` — Read — https://policylayer.com/tools/com-foliofact-foliofact/insider-feed.md
- `search` — Read — https://policylayer.com/tools/com-foliofact-foliofact/search.md
- `stock_financials` — Read — https://policylayer.com/tools/com-foliofact-foliofact/stock-financials.md
- `stock_insiders` — Read — https://policylayer.com/tools/com-foliofact-foliofact/stock-insiders.md
- `stock_options` — Read — https://policylayer.com/tools/com-foliofact-foliofact/stock-options.md
- `stock_earnings` — Write — https://policylayer.com/tools/com-foliofact-foliofact/stock-earnings.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=com-foliofact-foliofact · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-foliofact-foliofact