update_dashboard_item

Змінити НАЗВУ (підпис картки), іконку або позицію віджета дашборда. ⚠️ Підписи дашборда — окремі від назв таблиць: перейменування форм їх НЕ зачіпає, тож при перекладі інтерфейсу проєкту дашборд треба оновити цим інструментом окремо, інакше він лишиться попередньою мовою.

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Medium RISK CLASS

Category Write

Parameters 62 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-quintadb-mcp/update-dashboard-item.md

WHAT IT DOES

What update_dashboard_item does on QuintaDB

AI agents use update_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	—	Новий підпис картки
`app_id`	string	Yes	Project ID (from list_projects)
`item_id`	string	Yes	ID віджета з list_dashboard_items
`position`	integer	—	Позиція в сітці (опційно)
`portal_id`	string	—	Якщо не вказано — перший портал проєкту

Parameters from the server's own tool schema.

RISK

Why update_dashboard_item is rated Medium

An AI agent can call update_dashboard_item faster than any human can review: one bad instruction and it creates or modifies resources in QuintaDB by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_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 update_dashboard_item, this is the rule to start with:

update_dashboard_item Rate-limited

update_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_dashboard_item": {
      "limits": [
        {
          "counter": "update_dashboard_item_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect QuintaDB, apply this rule, and every update_dashboard_item call is checked against it from then on.

FAQ

Questions about update_dashboard_item

What does the update_dashboard_item tool do? +

What parameters does update_dashboard_item accept? +

update_dashboard_item accepts 6 parameters: icon, name, app_id, item_id, position, portal_id. Required: app_id, item_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_dashboard_item? +

Register the QuintaDB MCP server in PolicyLayer and add a rule for update_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 update_dashboard_item? +

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

Can I rate-limit update_dashboard_item? +

Yes. Add a rate_limit block to the update_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 update_dashboard_item completely? +

Set action: deny in the PolicyLayer policy for update_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 update_dashboard_item? +

update_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.

KEEP EXPLORING

More on QuintaDB, and thousands of servers like it.

This server

All 120 QuintaDB tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →