clerk.update_instance_settings

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

Medium RISK CLASS

Category Write

Parameters 90 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-settings.md

WHAT IT DOES

What clerk.update_instance_settings does on Vee3

AI agents use clerk.update_instance_settings 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
`hibp`	object	—	Whether Have I Been Pwned password checking should be enabled.
`test_mode`	object	—	Whether the instance should run in test mode.
`support_email`	object	—	Support email address shown to end users.
`allowed_origins`	object	—	Allowed browser origins for the instance.
`clerk_js_version`	object	—	Pinned Clerk.js version for the instance.
`clerk_instance_id`	object	—	Clerk instance id (ins_...) from clerk.get_connected_accounts. Omit to use the default connected account.
`development_origin`	object	—	Development origin URL for local testing.
`url_based_session_syncing`	object	—	Whether URL-based session syncing should be enabled.
`preferred_sign_in_strategy_when_password_required`	object	—	Preferred sign-in strategy when a password is required: "password" or "otp".

Parameters from the server's own tool schema.

RISK

Why clerk.update_instance_settings is rated Medium

Modifies application settings reversibly; high impact on authentication infrastructure but not destructive or financial.

From the tool's definition Update core settings for a connected Clerk application instance.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

clerk.update_instance_settings Rate-limited

clerk.update_instance_settings 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_settings": {
      "limits": [
        {
          "counter": "clerk.update_instance_settings_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_settings call is checked against it from then on.

FAQ

Questions about clerk.update_instance_settings

What does the clerk.update_instance_settings tool do? +

Update core settings for a connected Clerk application 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 settings. 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_settings accept? +

clerk.update_instance_settings accepts 9 parameters: hibp, test_mode, support_email, allowed_origins, clerk_js_version, clerk_instance_id, development_origin, url_based_session_syncing, preferred_sign_in_strategy_when_password_required. 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_settings? +

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

clerk.update_instance_settings 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_settings? +

Yes. Add a rate_limit block to the clerk.update_instance_settings 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_settings completely? +

Set action: deny in the PolicyLayer policy for clerk.update_instance_settings. 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_settings? +

clerk.update_instance_settings 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 →