add_dashboard_item
Додати віджет на дашборд порталу. Типи (module_type): 9=таблиця/звіт, 10=сума поля, 11=середнє поля, 12=кількість записів, 13=нові сьогодні, 14=оновлені сьогодні, 15=URL, 17=growth_by_table (динамічний ріст по таблиці), 18=growth_by_widgets (порівняння двох віджетів), 5=графік, 6=карта, 7=календа...
This record as markdown: /tools/com-quintadb-mcp/add-dashboard-item.md
What add_dashboard_item does on QuintaDB
AI agents use add_dashboard_item 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 |
|---|---|---|---|
icon | string | — | FontAwesome клас іконки (опційно, автовибір якщо не вказано) |
name | string | Yes | Назва віджету |
app_id | string | Yes | Project ID (from list_projects) |
currency | string | — | Символ валюти: $, €, ₴ тощо |
position | integer | — | Позиція в сітці (автоінкремент якщо не вказано) |
module_id | string | — | ID форми або звіту (для типів 9,10,11,12,13,14,17) / ID графіка(5) / карти(6) / календаря(7) |
portal_id | string | Yes | Portal ID (from list_portals or describe_project) |
block_width | integer | — | Ширина картки в сітці (1-12, bootstrap grid) |
module_type | integer | Yes | 9=таблиця/звіт, 10=сума, 11=середнє, 12=кількість, 13=нові сьогодні, 14=оновлені сьогодні, 15=URL, 17=growth_by_table, 18=growth_by_widgets, 5=графік, 6=карта, |
property_id | string | — | ID або назва числового поля — для суми(10), середнього(11). Для growth(17): поле що рахується. |
block_height | integer | — | Висота картки в px |
change_period | integer | — | Для growth: 0=вчора vs позавчора, 1=ця тиждень vs минулий, 2=цей місяць vs минулий, 3=квартал, 4=рік |
Parameters from the server's own tool schema.
Why add_dashboard_item is rated Medium
This tool creates new dashboard widgets/items, which modifies the portal's UI configuration reversibly. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or retrieve without side effects (Read). It is a Write operation because it creates or modifies dashboard elements.
From the tool's definition Tool name and description indicate adding/creating a dashboard item: 'add_dashboard_item' and 'Додати віджет на дашборд' (add widget to dashboard).
Risk signalsHigh parameter count (19 properties)
Attacks that exploit this kind of access
The rule that runs add_dashboard_item 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 add_dashboard_item, this is the rule to start with:
add_dashboard_item 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 add_dashboard_item call is checked against it from then on.
Questions about add_dashboard_item
Додати віджет на дашборд порталу. Типи (module_type): 9=таблиця/звіт, 10=сума поля, 11=середнє поля, 12=кількість записів, 13=нові сьогодні, 14=оновлені сьогодні, 15=URL, 17=growth_by_table (динамічний ріст по таблиці), 18=growth_by_widgets (порівняння двох віджетів), 5=графік, 6=карта, 7=календар, 16=HTML сторінка. Для growth по таблиці (17): вкажи module_id, date_property_id, change_period. Для growth по двох віджетах (18): first_widget_id та second_widget_id. 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.
add_dashboard_item accepts 12 parameters: icon, name, app_id, currency, position, module_id, portal_id, block_width, module_type, property_id, block_height, change_period. Required: name, app_id, portal_id, module_type. 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 add_dashboard_item: 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.
add_dashboard_item 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 add_dashboard_item 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 add_dashboard_item. 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.
add_dashboard_item 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