generate_ai_site
Згенерувати або оновити AI-лендинг порталу. Асинхронна операція — перевіряй статус через check_ai_site_status. Для редизайну передай existing_html з get_portal_page.
This record as markdown: /tools/com-quintadb-mcp/generate-ai-site.md
What generate_ai_site does on QuintaDB
AI agents use generate_ai_site to create or update resources in QuintaDB, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QuintaDB environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
app_id | string | Yes | Project ID (from list_projects) |
prompt | string | Yes | Опис сайту або інструкція по редизайну. Наприклад: 'Сучасний сайт клініки з формою запису' |
portal_id | string | Yes | Portal ID (from list_portals or describe_project) |
existing_html | string | — | Поточний HTML для редизайну (з get_portal_page). Якщо порожній — генерується з нуля. |
Parameters from the server's own tool schema.
Why generate_ai_site is rated Medium
This tool creates or modifies AI site landing pages, which falls under Write category—it changes portal content reversibly. While it affects a portal's public-facing interface, it is not destructive (can be reverted), not financial, and not code execution.
From the tool's definition The tool description states 'Згенерувати або оновити AI-лендинг порталу' (Generate or update AI landing portal). The terms 'генерувати' (generate) and 'оновити' (update) indicate creation and modification of portal content.
Attacks that exploit this kind of access
The rule that runs generate_ai_site safely
PolicyLayer is an MCP gateway: it sits between your AI agents and QuintaDB, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For generate_ai_site, this is the rule to start with:
generate_ai_site 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 QuintaDB, apply this rule, and every generate_ai_site call is checked against it from then on.
Questions about generate_ai_site
Згенерувати або оновити AI-лендинг порталу. Асинхронна операція — перевіряй статус через check_ai_site_status. Для редизайну передай existing_html з get_portal_page. It is categorised as a Write tool in the QuintaDB MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
generate_ai_site accepts 4 parameters: app_id, prompt, portal_id, existing_html. Required: app_id, prompt, portal_id. The full parameter table on this page comes from the server's own tool schema.
Register the QuintaDB MCP server in PolicyLayer and add a rule for generate_ai_site: 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 QuintaDB. Nothing to install.
generate_ai_site 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 generate_ai_site 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 generate_ai_site. 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.
generate_ai_site is provided by the QuintaDB MCP server (https://quintadb.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on QuintaDB, and thousands of servers like it.
This server
Across the catalogue