list_portal_groups
List portal user groups with members and permissions. (get portal groups, show client groups)
This record as markdown: /tools/com-quintadb-mcp/list-portal-groups.md
What list_portal_groups does on QuintaDB
AI agents call list_portal_groups to retrieve information from QuintaDB without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| 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) |
Parameters from the server's own tool schema.
Why list_portal_groups is rated Low
This tool retrieves and queries portal group information without side effects. It follows the 'Read' category pattern of fetching data for visibility/audit purposes. The low severity reflects minimal blast radius—exposure of group metadata is a disclosure risk but does not enable direct data manipulation or destructive actions. Confidence is high because the description uses unambiguous read-operation terminology.
From the tool's definition Tool description states 'List portal user groups' and aliases include 'get portal groups' and 'show client groups'. The verb 'list' and 'get' indicate retrieval operations.
Attacks that exploit this kind of access
The rule that runs list_portal_groups 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 list_portal_groups, this is the rule to start with:
list_portal_groups is read-only, so it stays allowed. 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 list_portal_groups call is checked against it from then on.
Questions about list_portal_groups
List portal user groups with members and permissions. (get portal groups, show client groups). It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.
list_portal_groups accepts 2 parameters: app_id, portal_id. Required: app_id, portal_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 list_portal_groups: 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.
list_portal_groups is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_portal_groups 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 list_portal_groups. 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.
list_portal_groups 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