aipush.pages.generate
Requires mip_status='ready' and cf_hostname_status='active' (check website_status first). Generates one AI-optimized HTML page structured for AI assistant answer compilation (ChatGPT, Perplexity, Gemini). Page includes decision question, short answer with CTA, comparison, pricing, FAQ. Published ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/aipush.pages.generate.md
What aipush.pages.generate does on Apibase
AI agents call aipush.pages.generate 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 |
|---|---|---|---|
keyword | string | — | Target keyword or topic for the page (e.g. "best hotels in Bangkok", "affordable dentist near me"). If omitted, the system picks from the semantic coverage grid |
website_domain | string | Yes | Domain of the website to generate a page for. Must be set up first via aipush.setup_website. |
Parameters from the server's own tool schema.
Why aipush.pages.generate is rated Low
Even though aipush.pages.generate 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.
Attacks that exploit this kind of access
The rule that runs aipush.pages.generate 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.generate, this is the rule to start with:
aipush.pages.generate 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.generate call is checked against it from then on.
Questions about aipush.pages.generate
Requires mip_status='ready' and cf_hostname_status='active' (check website_status first). Generates one AI-optimized HTML page structured for AI assistant answer compilation (ChatGPT, Perplexity, Gemini). Page includes decision question, short answer with CTA, comparison, pricing, FAQ. Published at reference.{domain}/{slug}. Optional keyword parameter targets specific search intent (AIPush). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
aipush.pages.generate accepts 2 parameters: keyword, website_domain. Required: 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.generate: 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.generate 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.generate 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.generate. 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.generate 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