create_team_group
Створити групу команди (внутрішній бек-офіс) з правами на форми/звіти. tables_permissions задає доступ одразу при створенні — передай масив з table (ID або назва форми/звіту), role (1=owner,2=read,3=write,4=creator,5=write no delete,6=read+edit+delete,7=read+edit), only_own_records, hidden_fields...
This record as markdown: /tools/com-quintadb-mcp/create-team-group.md
What create_team_group does on QuintaDB
AI agents use create_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 |
|---|---|---|---|
name | string | Yes | Назва групи |
app_id | string | Yes | Project ID (from list_projects) |
files_enabled | boolean | — | Доступ до файлів |
can_create_maps | boolean | — | |
can_delete_files | boolean | — | |
can_upload_files | boolean | — | |
can_create_charts | boolean | — | |
can_create_portals | boolean | — | |
has_access_to_team | boolean | — | |
tables_permissions | array | — | Права на форми/звіти |
can_create_calendars | boolean | — | |
can_create_newsletters | boolean | — |
Parameters from the server's own tool schema.
Why create_team_group is rated Medium
This tool creates new security groups and configures their permissions at creation time. While it modifies data structure rather than deleting it, the creation of groups with specific role-based access controls (owner, read, write, creator, etc.) and field-level visibility rules constitutes a material Write operation that affects system configuration and user access privileges.
From the tool's definition create_team_group — creates a team group with permissions for forms/reports. The tool performs irreversible group creation and assigns access controls (table_permissions with roles and field restrictions) that persist in the system.
Risk signalsHigh parameter count (17 properties)
Attacks that exploit this kind of access
The rule that runs create_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 create_team_group, this is the rule to start with:
create_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.
The button opens the PolicyLayer dashboard: create your workspace, connect QuintaDB, apply this rule, and every create_team_group call is checked against it from then on.
Questions about create_team_group
Створити групу команди (внутрішній бек-офіс) з правами на форми/звіти. tables_permissions задає доступ одразу при створенні — передай масив з table (ID або назва форми/звіту), role (1=owner,2=read,3=write,4=creator,5=write no delete,6=read+edit+delete,7=read+edit), only_own_records, hidden_fields (масив назв/ID полів що приховати). 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.
create_team_group accepts 12 parameters: name, app_id, files_enabled, can_create_maps, can_delete_files, can_upload_files, can_create_charts, can_create_portals, has_access_to_team, tables_permissions, can_create_calendars, can_create_newsletters. Required: name, app_id. The full parameter table on this page comes from the server's own tool schema.
Register the QuintaDB MCP server in PolicyLayer and add a rule for create_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.
create_team_group is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
More on QuintaDB, and thousands of servers like it.
This server
Across the catalogue