set_user_role
Призначити індивідуальну роль юзеру на проєкт або форму (окремо від груп). РОЛІ ТА ЩО ВОНИ ЗНАЧАТЬ (як їх бачить людина в інтерфейсі): owner = «Адмін» — повний доступ, як у власника, включно з правами і структурою; member = «Тільки читання»; writer = «Читання і запис»; writer_not_delete = «Читанн...
This record as markdown: /tools/com-quintadb-mcp/set-user-role.md
What set_user_role does on QuintaDB
AI agents use set_user_role 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 |
|---|---|---|---|
role | string | Yes | owner | member | writer | creator | writer_not_delete | read_edit_delete | read_and_edit |
email | string | Yes | Email юзера |
app_id | string | Yes | Project ID (from list_projects) |
entity_id | string | — | Опційно — обмежити роль конкретною формою |
Parameters from the server's own tool schema.
Why set_user_role is rated Medium
An AI agent can call set_user_role 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
The rule that runs set_user_role 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 set_user_role, this is the rule to start with:
set_user_role 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 set_user_role call is checked against it from then on.
Questions about set_user_role
Призначити індивідуальну роль юзеру на проєкт або форму (окремо від груп). РОЛІ ТА ЩО ВОНИ ЗНАЧАТЬ (як їх бачить людина в інтерфейсі): owner = «Адмін» — повний доступ, як у власника, включно з правами і структурою; member = «Тільки читання»; writer = «Читання і запис»; writer_not_delete = «Читання і запис без видалення»; read_edit_delete = «Читання, редагування, видалення»; read_and_edit = «Читання і редагування»; creator = «Читання, запис, створення форм». Коли людина каже «зроби її адміном» — це owner. 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.
set_user_role accepts 4 parameters: role, email, app_id, entity_id. Required: role, email, 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 set_user_role: 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.
set_user_role 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 set_user_role 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 set_user_role. 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.
set_user_role 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