clerk.unban_users
Remove bans from one or more Clerk users, restoring their ability to sign in. Call clerk.get_connected_accounts first. Pass clerk_instance_id to target a specific connection, or omit it to use the default account. Returns the updated user summaries and total count. Cost = 8 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/clerk.unban-users.md
What clerk.unban_users does on Vee3
AI agents use clerk.unban_users to create or update resources in Vee3, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vee3 environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
user_ids | array | Yes | List of one or more Clerk user ids (user_...) to unban. |
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.unban_users is rated Medium
Restores sign-in access for banned users, reversible but high security impact.
From the tool's definition Remove bans from one or more Clerk users, restoring their ability to sign in
Attacks that exploit this kind of access
The rule that runs clerk.unban_users 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.unban_users, this is the rule to start with:
clerk.unban_users 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 Vee3, apply this rule, and every clerk.unban_users call is checked against it from then on.
Questions about clerk.unban_users
Remove bans from one or more Clerk users, restoring their ability to sign in. Call clerk.get_connected_accounts first. Pass clerk_instance_id to target a specific connection, or omit it to use the default account. Returns the updated user summaries and total count. Cost = 8 tokens. It is categorised as a Write tool in the Vee3 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
clerk.unban_users accepts 2 parameters: user_ids, clerk_instance_id. Required: user_ids. 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.unban_users: 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.unban_users 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 clerk.unban_users 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.unban_users. 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.unban_users 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