add_user_to_team_group

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Medium RISK CLASS

Category Write

Parameters 53 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-team-group.md

WHAT IT DOES

What add_user_to_team_group does on QuintaDB

AI agents use add_user_to_team_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)
`send_email`	boolean	—	Mail the invitation letter to a NEW account (default true). false: nobody is told a password — the person sets their own from the sign-in page.
`user_group_id`	string	Yes	ID групи (з list_team_groups або create_team_group)
`move_from_other_groups`	boolean	—	Видалити юзера з усіх інших груп і скинути індивідуальні ролі (default false)

Parameters from the server's own tool schema.

RISK

Why add_user_to_team_group is rated Medium

An AI agent can call add_user_to_team_group 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.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

add_user_to_team_group Rate-limited

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

FAQ

Questions about add_user_to_team_group

What does the add_user_to_team_group tool do? +

Add a person to a team group by email. An account is created when there is none. The new account gets a password of its own, which only the invitation letter shows (with a one-time link that signs the person in); the answer's invitation says what was mailed. Never tell anyone a password. move_from_other_groups=true takes the person out of every other group and resets their individual roles (a full move into this group). 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_team_group accept? +

add_user_to_team_group accepts 5 parameters: email, app_id, send_email, user_group_id, move_from_other_groups. Required: email, app_id, user_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_team_group? +

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

add_user_to_team_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_team_group? +

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

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

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

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb →team_manager_emit_decision on Team Manager MCP → The MCP Attack Database →

Guides

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