check_ai_site_status
Перевірити статус генерації AI-сайту. Викликай кожні 10-15 сек після generate_ai_site. Повертає: pending / success / error.
This record as markdown: /tools/com-quintadb-mcp/check-ai-site-status.md
What check_ai_site_status does on QuintaDB
AI agents call check_ai_site_status to retrieve information from QuintaDB 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 |
|---|---|---|---|
app_id | string | Yes | Project ID (from list_projects) |
portal_id | string | Yes | Portal ID (from list_portals or describe_project) |
Parameters from the server's own tool schema.
Why check_ai_site_status is rated Low
This tool retrieves the current state of an AI-site generation process. It performs no mutations, does not execute code or commands, and has no destructive potential. The narrow scope (polling a single status field) and informational nature classify it as Read category with low severity. Misuse by an agent would only allow repeated status checks, posing minimal security risk.
From the tool's definition Tool description states it checks the status of AI-site generation and returns pending/success/error—a read-only query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs check_ai_site_status 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 check_ai_site_status, this is the rule to start with:
check_ai_site_status 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 QuintaDB, apply this rule, and every check_ai_site_status call is checked against it from then on.
Questions about check_ai_site_status
Перевірити статус генерації AI-сайту. Викликай кожні 10-15 сек після generate_ai_site. Повертає: pending / success / error. It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.
check_ai_site_status accepts 2 parameters: app_id, portal_id. Required: app_id, 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 check_ai_site_status: 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.
check_ai_site_status 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 check_ai_site_status 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 check_ai_site_status. 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.
check_ai_site_status 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