list_user_roles
Список індивідуальних ролей юзерів у проєкті (окрім групових прав).
This record as markdown: /tools/com-quintadb-mcp/list-user-roles.md
What list_user_roles does on QuintaDB
AI agents call list_user_roles 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) |
Parameters from the server's own tool schema.
Why list_user_roles is rated Low
This tool queries and returns user role information without creating, modifying, deleting, or executing any operations. It is a read-only data retrieval function that has no side effects on the system. The scope is limited to listing existing role assignments, making it a standard Read category tool with low severity (sensitive information exposure is possible but limited to role metadata).
From the tool's definition Tool name 'list_user_roles' and description indicating it retrieves/lists roles of users in a project ('Список індивідуальних ролей юзерів у проєкті' = 'List of individual user roles in the project').
Attacks that exploit this kind of access
The rule that runs list_user_roles 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_user_roles, this is the rule to start with:
list_user_roles 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_user_roles call is checked against it from then on.
Questions about list_user_roles
Список індивідуальних ролей юзерів у проєкті (окрім групових прав). It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.
list_user_roles accepts 1 parameter: app_id. Required: app_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_user_roles: 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_user_roles 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_user_roles 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_user_roles. 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_user_roles 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