clerk.update_instance_restrictions

SERVERVee3 SOURCEhttps://mcp.vee3.io/mcp

Medium RISK CLASS

Category Write

Parameters 60 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vee3io-vee3/clerk.update-instance-restrictions.md

WHAT IT DOES

What clerk.update_instance_restrictions does on Vee3

AI agents use clerk.update_instance_restrictions 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
`allowlist`	object	—	Whether the allowlist restriction should be enabled.
`blocklist`	object	—	Whether the blocklist restriction should be enabled.
`clerk_instance_id`	object	—	Clerk instance id (ins_...) from clerk.get_connected_accounts. Omit to use the default connected account.
`block_email_subaddresses`	object	—	Whether email subaddresses (plus-addressing) should be blocked.
`block_disposable_email_domains`	object	—	Whether disposable email domains should be blocked.
`allowlist_blocklist_disabled_on_sign_in`	object	—	Whether allowlist and blocklist checks should be skipped during sign-in.

Parameters from the server's own tool schema.

RISK

Why clerk.update_instance_restrictions is rated Medium

Modifies authentication configuration reversibly, affecting user access policies but not destroying data or executing arbitrary code.

From the tool's definition Update sign-up and sign-in restriction settings for a connected Clerk instance

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clerk.update_instance_restrictions 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.update_instance_restrictions, this is the rule to start with:

clerk.update_instance_restrictions Rate-limited

clerk.update_instance_restrictions 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "clerk.update_instance_restrictions": {
      "limits": [
        {
          "counter": "clerk.update_instance_restrictions_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Vee3, apply this rule, and every clerk.update_instance_restrictions call is checked against it from then on.

FAQ

Questions about clerk.update_instance_restrictions

What does the clerk.update_instance_restrictions tool do? +

Update sign-up and sign-in restriction settings for a connected Clerk instance. 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 instance restrictions. 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.

What parameters does clerk.update_instance_restrictions accept? +

clerk.update_instance_restrictions accepts 6 parameters: allowlist, blocklist, clerk_instance_id, block_email_subaddresses, block_disposable_email_domains, allowlist_blocklist_disabled_on_sign_in. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on clerk.update_instance_restrictions? +

Register the Vee3 MCP server in PolicyLayer and add a rule for clerk.update_instance_restrictions: 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.

What risk level is clerk.update_instance_restrictions? +

clerk.update_instance_restrictions is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit clerk.update_instance_restrictions? +

Yes. Add a rate_limit block to the clerk.update_instance_restrictions 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.

How do I block clerk.update_instance_restrictions completely? +

Set action: deny in the PolicyLayer policy for clerk.update_instance_restrictions. 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.

What MCP server provides clerk.update_instance_restrictions? +

clerk.update_instance_restrictions 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.

KEEP EXPLORING

More on Vee3, and thousands of servers like it.

This server

All 249 Vee3 tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →