set_table_permission
What a group (team or portal) may do on a table or report, and whether its people see ONLY THEIR OWN records there. For a group that already has rights on the table pass ONLY what the person asked to change: «technicians see only their own orders» is only_own_records: true with NO role — a role y...
This record as markdown: /tools/com-quintadb-mcp/set-table-permission.md
What set_table_permission does on QuintaDB
AI agents use set_table_permission 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 | integer | — | 1=owner, 2=read, 3=write, 4=create, 5=write no delete, 6=read+edit+delete, 7=read+edit. Needed only for a group with no rights on this table yet; otherwise leav |
app_id | string | Yes | Project ID (from list_projects) |
revoke | boolean | — | true — ЗАБРАТИ право цієї групи на цю форму/звіт (правило видаляється). Ролі 1..7 не мають значення «нема доступу», тож відкликати можна лише так. role при revo |
entity_id | string | Yes | ID форми або звіту |
hidden_fields | array | — | Поля (назви або ID), які ця група НЕ бачить у ФОРМІ запису. Так звужують форму: напр. рядовий працівник заповнює сім полів ліда замість усіх тридцяти трьох. Пер |
user_group_id | string | — | ID team групи (з create_team_group) |
hidden_columns | array | — | Поля (назви або ID), яких ця група НЕ бачить у ТАБЛИЦІ (списку записів). Незалежне від hidden_fields: поле можна лишити у формі, але прибрати з таблиці. Та сама |
portal_group_id | string | — | ID portal групи |
only_own_records | boolean | — | true: people of this group see only the records they added or were made owner of. false: they see everyone's. |
add_related_records | boolean | — | Кнопка «додати повʼязаний запис» у картці (працює разом із show_related_records). |
view_record_history | boolean | — | Дозволити цій групі бачити вкладку «Історія» змін запису (хто, коли, що було → що стало). За замовчуванням вимкнено: історія показує старі значення полів. |
show_related_records | boolean | — | Показувати в картці запису блок повʼязаних записів з інших таблиць (напр. у картці працівника — його рядки зарплати). Без цього група бачить лише саму картку, н |
Parameters from the server's own tool schema.
Why set_table_permission is rated Medium
An AI agent can call set_table_permission 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 signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs set_table_permission 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_table_permission, this is the rule to start with:
set_table_permission 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_table_permission call is checked against it from then on.
Questions about set_table_permission
What a group (team or portal) may do on a table or report, and whether its people see ONLY THEIR OWN records there. For a group that already has rights on the table pass ONLY what the person asked to change: «technicians see only their own orders» is only_own_records: true with NO role — a role you pass replaces the group's present one. The answer says CHANGED / UNCHANGED for the role and for only_own_records, and what «own» means: repeat that meaning, never «assigned to them». Встановити права групи (team або portal) на форму/звіт. role: 1=owner («Адмін» в інтерфейсі — повний доступ, як у власника: дані, структура, права), 2=read (тільки читання), 3=write (читання і запис), 4=creator (читання, запис, створення форм), 5=write no delete (без видалення), 6=read+edit+delete, 7=read+edit. Коли людина просить «зроби адміном / хай бачить усе, як я» — це role 1. Передати або user_group_id (team) або portal_group_id (portal). 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_table_permission accepts 12 parameters: role, app_id, revoke, entity_id, hidden_fields, user_group_id, hidden_columns, portal_group_id, only_own_records, add_related_records, view_record_history, show_related_records. Required: app_id, entity_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_table_permission: 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_table_permission 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_table_permission 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_table_permission. 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_table_permission 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