update_portal_settings

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Medium RISK CLASS

Category Write

Parameters 92 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-portal-settings.md

WHAT IT DOES

What update_portal_settings does on QuintaDB

AI agents use update_portal_settings 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
`name`	string	—	Display name
`color`	integer	—	The colour: 0=White, 1=Black, 2=Grey, 3=Blue, 4=Green, 5=Orange, 6=Red. In themes 0, 1, 3, 4, 12, 13 0 is a light menu with dark letters, and 1–6 a menu of that
`theme`	integer	—	The theme, which also decides where the menu is: 0=Standard (menu: a bar across the top), 1=Professional (menu: a narrow strip of icons on the left that opens o
`app_id`	string	Yes	Project ID (from list_projects)
`locale`	string	—	en, uk, ru, ...
`auth_type`	integer	—	The portal's sign-in (the login window): 0=public: anyone with the link gets in, no sign-in; 1=one shared login and password for everyone; 2=sign-in required: e
`portal_id`	string	Yes	Portal ID (from list_portals or describe_project)
`subdomain`	string	—	The subdomain without .quintadb.com
`self_registration`	boolean	—	true = a visitor can create their own account on the portal's login page; false = accounts only by invitation. Pass it ONLY when the person asked for exactly th

Parameters from the server's own tool schema.

RISK

Why update_portal_settings is rated Medium

An AI agent can call update_portal_settings 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_portal_settings 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_portal_settings, this is the rule to start with:

update_portal_settings Rate-limited

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

FAQ

Questions about update_portal_settings

What does the update_portal_settings tool do? +

Change a portal's settings: name, subdomain, locale, theme, colour, sign-in type (the login window), whether people can register themselves. The answer says where the menu is now (menu) and whether the change moved it (menu_moved), who gets into the portal now (access), whether your call changed that (access_changed) and whether people can create their own accounts (self_registration). 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 update_portal_settings accept? +

update_portal_settings accepts 9 parameters: name, color, theme, app_id, locale, auth_type, portal_id, subdomain, self_registration. 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 update_portal_settings? +

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

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

Can I rate-limit update_portal_settings? +

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

Set action: deny in the PolicyLayer policy for update_portal_settings. 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_portal_settings? +

update_portal_settings 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 150 QuintaDB tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

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