set_module_permission
Дозволити або заборонити доступ до модуля (forms, charts, maps, ...) для групи.
This record as markdown: /tools/com-quintadb-mcp/set-module-permission.md
What set_module_permission does on QuintaDB
AI agents use set_module_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 |
|---|---|---|---|
app_id | string | Yes | Project ID (from list_projects) |
module | string | Yes | forms, charts, maps, calendars, files, team, portals, reports, table |
can_edit | boolean | — | |
module_id | string | — | ID конкретного модуля (entity/widget/chart/map...) |
can_delete | boolean | — | |
user_group_id | string | — | ID team group (або portal_group_id) |
portal_group_id | string | — | Portal group ID (from list_portal_groups or create_portal_group) |
Parameters from the server's own tool schema.
Why set_module_permission is rated Medium
This tool creates or modifies access control settings—specifically permission grants or denials for user groups to access modules. Permission changes are reversible (permissions can be granted again), placing it in the Write category rather than Destructive.
From the tool's definition Tool description states 'Дозволити або заборонити доступ до модуля' (Allow or forbid access to module) for a group. This modifies permission configurations for forms, charts, maps, etc.
Attacks that exploit this kind of access
The rule that runs set_module_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_module_permission, this is the rule to start with:
set_module_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_module_permission call is checked against it from then on.
Questions about set_module_permission
Дозволити або заборонити доступ до модуля (forms, charts, maps, ...) для групи. 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_module_permission accepts 7 parameters: app_id, module, can_edit, module_id, can_delete, user_group_id, portal_group_id. Required: app_id, module. 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_module_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_module_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_module_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_module_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_module_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