aipush.pages.content
Get full HTML content and metadata of a specific generated page by slug (AIPush)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/aipush.pages.content.md
What aipush.pages.content does on Apibase
AI agents call aipush.pages.content 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 |
|---|---|---|---|
slug | string | Yes | Page slug identifier (e.g. "best-hotels-bangkok-2026"). Returned by aipush.list_pages or aipush.generate_page. |
website_domain | string | Yes | Domain the page belongs to (e.g. "example.com"). |
Parameters from the server's own tool schema.
Why aipush.pages.content is rated Low
Retrieves static page content and metadata without side effects; no data creation, modification, or execution.
From the tool's definition Get full HTML content and metadata of a specific generated page by slug
Attacks that exploit this kind of access
The rule that runs aipush.pages.content 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 aipush.pages.content, this is the rule to start with:
aipush.pages.content 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 aipush.pages.content call is checked against it from then on.
Questions about aipush.pages.content
Get full HTML content and metadata of a specific generated page by slug (AIPush). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
aipush.pages.content accepts 2 parameters: slug, website_domain. Required: slug, website_domain. 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 aipush.pages.content: 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.
aipush.pages.content 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 aipush.pages.content 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 aipush.pages.content. 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.
aipush.pages.content 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