govuk.content.fetch
Fetch full content of a GOV.UK page by its base path — title, publication date, organisation, full HTML body (or structured fields per content type), related documents.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/govuk.content.fetch.md
What govuk.content.fetch does on Apibase
AI agents call govuk.content.fetch to retrieve information from Apibase 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 |
|---|---|---|---|
base_path | string | Yes | GOV.UK URL path starting with /, e.g. '/income-tax-rates' or '/government/publications/spring-statement-2026'. Get from govuk.search results. |
Parameters from the server's own tool schema.
Why govuk.content.fetch is rated Low
Tool retrieves and queries publicly available government web content with no side effects or modifications.
From the tool's definition Fetch full content of a GOV.UK page by its base path
Attacks that exploit this kind of access
The rule that runs govuk.content.fetch safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For govuk.content.fetch, this is the rule to start with:
govuk.content.fetch 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 Apibase, apply this rule, and every govuk.content.fetch call is checked against it from then on.
Questions about govuk.content.fetch
Fetch full content of a GOV.UK page by its base path — title, publication date, organisation, full HTML body (or structured fields per content type), related documents. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
govuk.content.fetch accepts 1 parameter: base_path. Required: base_path. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for govuk.content.fetch: 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 Apibase. Nothing to install.
govuk.content.fetch 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 govuk.content.fetch 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 govuk.content.fetch. 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.
govuk.content.fetch is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue