create_report
Створити звіт (фільтр/view) для форми. Підтримує умови фільтрації, групування, суму/середнє по групі, видимі колонки, сортування. Для дат: yesterday, today, last_7_days, last_30_days, this_month, this_week, between (+ from/to), before, after тощо.
This record as markdown: /tools/com-quintadb-mcp/create-report.md
What create_report does on QuintaDB
AI agents use create_report 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 |
|---|---|---|---|
asc | boolean | — | true=за зростанням (default), false=за спаданням. Застосовується до sort_by. |
name | string | Yes | Назва звіту |
order | string | — | asc або desc — напрям сортування ГРУП (лише коли задано group_field_ids). Це НЕ поле для сортування — для цього використовуй sort_by. |
app_id | string | Yes | Project ID (from list_projects) |
sort_by | string | — | ID або назва поля для сортування записів (використовується разом з asc). |
per_page | integer | — | Записів на сторінку (default 10) |
criterias | array | — | Умови фільтрації. Для дат: yesterday, today, last_7_days, last_30_days, this_week, this_month, next_7_days, between (+ from/to), before, after. Для текстів: is, |
entity_id | string | Yes | Form ID (from list_forms or describe_project) |
property_ids | array | — | ID або назви полів що відображаються (пусто = всі) |
total_by_group | integer | — | 1 = показати суму числового поля по кожній групі. Обов'язково вказати total_by_group_column_id. |
group_field_ids | array | — | ID полів для групування (GROUP BY). Наприклад, групувати по статусу. |
average_by_group | integer | — | 1 = показати середнє числового поля по кожній групі. Обов'язково вказати average_by_group_column_id. |
Parameters from the server's own tool schema.
Why create_report is rated Medium
This tool creates a new report or view configuration for a form, including filters, groupings, aggregations, and sorting. It persistently creates a new object in the system (a report/filter/view), which is a reversible write operation. It does not delete data or execute code, so Write is the appropriate category.
From the tool's definition Створити звіт (фільтр/view) для форми — 'Створити' means 'Create' in Ukrainian, indicating creation of a new report/view object
Risk signalsHigh parameter count (22 properties)
Attacks that exploit this kind of access
The rule that runs create_report 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 create_report, this is the rule to start with:
create_report 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 create_report call is checked against it from then on.
Questions about create_report
Створити звіт (фільтр/view) для форми. Підтримує умови фільтрації, групування, суму/середнє по групі, видимі колонки, сортування. Для дат: yesterday, today, last_7_days, last_30_days, this_month, this_week, between (+ from/to), before, after тощо. 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.
create_report accepts 12 parameters: asc, name, order, app_id, sort_by, per_page, criterias, entity_id, property_ids, total_by_group, group_field_ids, average_by_group. Required: name, app_id, entity_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 create_report: 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.
create_report 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 create_report 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 create_report. 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.
create_report 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