delete_portal_group
Видалити групу порталу разом з правами і учасниками.
This record as markdown: /tools/com-quintadb-mcp/delete-portal-group.md
What delete_portal_group does on QuintaDB
AI agents call delete_portal_group to permanently remove resources in QuintaDB, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
app_id | string | Yes | Project ID (from list_projects) |
portal_id | string | Yes | Portal ID (from list_portals or describe_project) |
portal_group_id | string | Yes | Portal group ID (from list_portal_groups or create_portal_group) |
Parameters from the server's own tool schema.
Why delete_portal_group is rated Critical
This tool permanently removes a portal group and all its associated data (rights and members). Deletion cannot be undone and represents irreversible destruction of data and access configurations.
From the tool's definition Tool name 'delete_portal_group' and description 'Видалити групу порталу разом з правами і учасниками' (Ukrainian: 'Delete portal group together with rights and members') explicitly indicates irreversible deletion of a group entity along with associated…
Attacks that exploit this kind of access
The rule that runs delete_portal_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 delete_portal_group, this is the rule to start with:
delete_portal_group is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect QuintaDB, apply this rule, and every delete_portal_group call is checked against it from then on.
Questions about delete_portal_group
Видалити групу порталу разом з правами і учасниками. It is categorised as a Destructive tool in the QuintaDB MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_portal_group accepts 3 parameters: app_id, portal_id, portal_group_id. Required: app_id, portal_id, portal_group_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 delete_portal_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.
delete_portal_group is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_portal_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 delete_portal_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.
delete_portal_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.
Across the catalogue