add_dashboard_item

Додати віджет на дашборд порталу. Типи (module_type): 9=таблиця/звіт, 10=сума поля, 11=середнє поля, 12=кількість записів, 13=нові сьогодні, 14=оновлені сьогодні, 15=URL, 17=growth_by_table (динамічний ріст по таблиці), 18=growth_by_widgets (порівняння двох віджетів), 5=графік, 6=карта, 7=календа...

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp
Medium RISK CLASS
Category Write
Parameters 124 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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)

Questions about add_dashboard_item

What does the add_dashboard_item tool do? +

Додати віджет на дашборд порталу. Типи (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.

What parameters does add_dashboard_item accept? +

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.

How do I enforce a policy on add_dashboard_item? +

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.

What risk level is add_dashboard_item? +

add_dashboard_item is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_dashboard_item? +

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.

How do I block add_dashboard_item completely? +

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.

What MCP server provides add_dashboard_item? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of QuintaDB's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.