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).
This record as markdown: /tools/com-foliofact-foliofact/fetch-page.md
What fetch_page does on FolioFact
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.
| 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.
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 signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs fetch_page safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FolioFact, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fetch_page, this is the rule to start with:
fetch_page is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FolioFact, apply this rule, and every fetch_page call is checked against it from then on.
Questions about 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). It is categorised as a Read tool in the FolioFact MCP Server, which means it retrieves data without modifying state.
fetch_page accepts 1 parameter: path. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the FolioFact MCP server in PolicyLayer and add a rule for fetch_page: 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 FolioFact. Nothing to install.
fetch_page is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the fetch_page 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 fetch_page. 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.
fetch_page is provided by the FolioFact MCP server (https://foliofact.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FolioFact, and thousands of servers like it.
This server
Across the catalogue