clerk.list_organization_roles
List organization roles in a connected Clerk application. Call clerk.get_connected_accounts first. Pass clerk_instance_id to target a specific connection, or omit it to use the default account. Returns role summaries with nested permissions and total_count. Cost = 5 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/clerk.list-organization-roles.md
What clerk.list_organization_roles does on Vee3
AI agents call clerk.list_organization_roles to retrieve information from Vee3 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 |
|---|---|---|---|
limit | integer | — | Maximum number of results to return (1–500). |
query | object | — | Search by name or key. |
offset | integer | — | Number of results to skip before returning. |
order_by | object | — | Sort order with optional + or - prefix (for example -created_at or name). Defaults to -created_at. |
clerk_instance_id | object | — | Clerk instance id (ins_...) from clerk.get_connected_accounts. Omit to use the default connected account. |
Parameters from the server's own tool schema.
Why clerk.list_organization_roles is rated Low
Lists roles and permissions without modification, creation, deletion, or financial impact.
From the tool's definition List organization roles, returns role summaries with nested permissions
Attacks that exploit this kind of access
The rule that runs clerk.list_organization_roles safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clerk.list_organization_roles, this is the rule to start with:
clerk.list_organization_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 Vee3, apply this rule, and every clerk.list_organization_roles call is checked against it from then on.
Questions about clerk.list_organization_roles
List organization roles in a connected Clerk application. Call clerk.get_connected_accounts first. Pass clerk_instance_id to target a specific connection, or omit it to use the default account. Returns role summaries with nested permissions and total_count. Cost = 5 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
clerk.list_organization_roles accepts 5 parameters: limit, query, offset, order_by, clerk_instance_id. The full parameter table on this page comes from the server's own tool schema.
Register the Vee3 MCP server in PolicyLayer and add a rule for clerk.list_organization_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 Vee3. Nothing to install.
clerk.list_organization_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 clerk.list_organization_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 clerk.list_organization_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.
clerk.list_organization_roles is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vee3, and thousands of servers like it.
This server
Across the catalogue