set_table_permission

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Medium RISK CLASS

Category Write

Parameters 63 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-quintadb-mcp/set-table-permission.md

WHAT IT DOES

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	Yes	1=owner, 2=read, 3=write, 4=create, 5=write no delete, 6=read+edit+delete, 7=read+edit
`app_id`	string	Yes	Project ID (from list_projects)
`entity_id`	string	Yes	ID форми або звіту
`user_group_id`	string	—	ID team групи (з create_team_group)
`portal_group_id`	string	—	ID portal групи
`only_own_records`	boolean	—	Бачить тільки свої записи

Parameters from the server's own tool schema.

RISK

Why set_table_permission is rated Medium

This tool modifies access control settings by assigning write and edit permissions to groups. While it doesn't directly create or delete records, it enables those capabilities for other users/groups. The most severe role offered is 'read+edit+delete' (role 6), which grants destructive permissions, but the tool itself is performing reversible permission assignment rather than irreversible data destruction.

From the tool's definition Tool description indicates it sets permissions on forms/reports with roles including 'writer' (role 3), 'creator' (role 4), 'write no delete' (role 5), and 'read+edit+delete' (role 6).

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_table_permission": {
      "limits": [
        {
          "counter": "set_table_permission_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 set_table_permission call is checked against it from then on.

FAQ

Questions about set_table_permission

What does the set_table_permission tool do? +

Встановити права групи (team або portal) на форму/звіт. role: 1=owner, 2=read only, 3=writer, 4=creator, 5=write no delete, 6=read+edit+delete, 7=read+edit. Передати або 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.

What parameters does set_table_permission accept? +

set_table_permission accepts 6 parameters: role, app_id, entity_id, user_group_id, portal_group_id, only_own_records. Required: role, app_id, entity_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on set_table_permission? +

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.

What risk level is set_table_permission? +

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

Can I rate-limit set_table_permission? +

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.

How do I block set_table_permission completely? +

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.

What MCP server provides set_table_permission? +

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.

KEEP EXPLORING

More on QuintaDB, and thousands of servers like it.

This server

All 116 QuintaDB tools →

Across the catalogue

set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

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