add_portal_menu_item

Додати пункт меню порталу. Top-level: module_ai_id + module_id. Підменю-група: module_ai_id='submenu' + name (без module_id). Підпункт: parent_section_id + module_ai_id + module_id. Типи module_ai_id: form_ID/table_ID=форма, report_ID=звіт, map_ID=карта, cal_ID=календар, chart_ID=графік.

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Medium RISK CLASS

Category Write

Parameters 102 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-portal-menu-item.md

WHAT IT DOES

What add_portal_menu_item does on QuintaDB

AI agents use add_portal_menu_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
`url`	string	—	URL для module_type=12
`icon`	string	—	FontAwesome клас іконки
`name`	string	—	Назва пункту меню
`app_id`	string	Yes	Project ID (from list_projects)
`position`	integer	—	Позиція в меню
`module_id`	string	—	Реальний ID модуля (форми, звіту, карти тощо). Не потрібен для submenu-групи.
`portal_id`	string	Yes	Portal ID (from list_portals or describe_project)
`module_type`	integer	—	Альтернатива module_ai_id: 10=підменю, 12=URL, 13=HTML-сторінка
`module_ai_id`	string	—	form_ID, table_ID, report_ID, map_ID, cal_ID, chart_ID, або 'submenu' для групи підменю
`parent_section_id`	string	—	ID батьківської секції підменю (з list_portal_menu_items) — для підпунктів

Parameters from the server's own tool schema.

RISK

Why add_portal_menu_item is rated Medium

This tool creates new menu items and organizes portal navigation, which is a reversible data modification operation. It does not retrieve data (Read), execute arbitrary code (Execute), delete items (Destructive), or handle payments (Financial). The 'add_' prefix combined with portal structure modification confirms Write category.

From the tool's definition add_portal_menu_item creates or modifies portal menu structure by adding menu items at various levels (top-level, submenu groups, submenus).

Risk signalsAccepts URL/endpoint input (url) · High parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

add_portal_menu_item Rate-limited

add_portal_menu_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": {
    "add_portal_menu_item": {
      "limits": [
        {
          "counter": "add_portal_menu_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 add_portal_menu_item call is checked against it from then on.

FAQ

Questions about add_portal_menu_item

What does the add_portal_menu_item tool do? +

What parameters does add_portal_menu_item accept? +

add_portal_menu_item accepts 10 parameters: url, icon, name, app_id, position, module_id, portal_id, module_type, module_ai_id, parent_section_id. Required: app_id, portal_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on add_portal_menu_item? +

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

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

Can I rate-limit add_portal_menu_item? +

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

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

add_portal_menu_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 116 QuintaDB tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb →add_video on Mcptube Vision → The MCP Attack Database →

Guides

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