add_user_to_portal_group

Додати юзера до групи порталу за email. Якщо юзер не існує в порталі — буде створений. move_from_other_groups (default false) — перемістити з інших груп.

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Medium RISK CLASS

Category Write

Parameters 64 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-user-to-portal-group.md

WHAT IT DOES

What add_user_to_portal_group does on QuintaDB

AI agents use add_user_to_portal_group 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
`email`	string	Yes	User email address
`app_id`	string	Yes	Project ID (from list_projects)
`portal_id`	string	Yes	Portal ID (from list_portals or describe_project)
`send_email`	boolean	—	Відправити activation email (default true)
`portal_group_id`	string	Yes	ID групи (з list_portal_groups або create_portal_group)
`move_from_other_groups`	boolean	—	Видалити з усіх інших груп цього порталу (default false)

Parameters from the server's own tool schema.

RISK

Why add_user_to_portal_group is rated Medium

This tool creates new users and modifies group membership—both reversible write operations. It does not delete data (would be Destructive), does not execute arbitrary code (would be Execute), and does not involve financial transactions (would be Financial).

From the tool's definition Tool description states 'Додати юзера до групи порталу' (add user to portal group) and 'Якщо юзер не існує в порталі — буде створений' (if user does not exist in portal—will be created).

Attacks that exploit this kind of access

RECOMMENDED RULE

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

add_user_to_portal_group Rate-limited

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

FAQ

Questions about add_user_to_portal_group

What does the add_user_to_portal_group tool do? +

Додати юзера до групи порталу за email. Якщо юзер не існує в порталі — буде створений. move_from_other_groups (default false) — перемістити з інших груп. 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_user_to_portal_group accept? +

add_user_to_portal_group accepts 6 parameters: email, app_id, portal_id, send_email, portal_group_id, move_from_other_groups. Required: email, app_id, portal_id, portal_group_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on add_user_to_portal_group? +

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

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

Can I rate-limit add_user_to_portal_group? +

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

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

add_user_to_portal_group 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 →