aipush.website.setup
Register a website for AI marketing. Call with domain + target_url. If DNS is not configured, returns DNS_NOT_VERIFIED with exact CNAME record instructions — relay to user: reference.{domain} → cname.aipush.app. After user creates DNS record, call again. On success: client registered, MIP analysi...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/aipush.website.setup.md
What aipush.website.setup does on Apibase
AI agents use aipush.website.setup to create or update resources in Apibase, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apibase environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
target_url | string | Yes | Target conversion URL — the single page all generated content will link to (e.g. "https://example.com/book", "https://myhotel.com/reserve"). Must be on the same |
website_domain | string | Yes | Domain of the website to register (e.g. "example.com", "myhotel.com"). Must have a CNAME record: reference.{domain} → cname.aipush.app |
Parameters from the server's own tool schema.
Why aipush.website.setup is rated Medium
Creates and registers a new website configuration; reversible registration with external service.
From the tool's definition Register a website for AI marketing... client registered, SSL provisioning begins
Attacks that exploit this kind of access
The rule that runs aipush.website.setup 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.website.setup, this is the rule to start with:
aipush.website.setup stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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.website.setup call is checked against it from then on.
Questions about aipush.website.setup
Register a website for AI marketing. Call with domain + target_url. If DNS is not configured, returns DNS_NOT_VERIFIED with exact CNAME record instructions — relay to user: reference.{domain} → cname.aipush.app. After user creates DNS record, call again. On success: client registered, MIP analysis starts automatically, SSL provisioning begins. Poll website_status until mip_status='ready' and cf_hostname_status='active', then use generate_page. Idempotent (AIPush). It is categorised as a Write tool in the Apibase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
aipush.website.setup accepts 2 parameters: target_url, website_domain. Required: target_url, 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.website.setup: 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.website.setup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the aipush.website.setup 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.website.setup. 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.website.setup 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