clerk.update_enterprise_connection
Update an enterprise SSO connection 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 the updated enterprise_connection summary. Cost = 8 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/clerk.update-enterprise-connection.md
What clerk.update_enterprise_connection does on Vee3
AI agents use clerk.update_enterprise_connection 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 |
|---|---|---|---|
name | object | — | Updated display name for the connection. |
oidc | object | — | Updated OIDC client configuration. |
saml | object | — | Updated SAML IdP configuration. |
active | object | — | Whether the connection is active. |
domains | object | — | Updated domain list (replaces existing domains when provided). |
connection_id | string | Yes | Clerk enterprise connection id (entc_...) to retrieve, update, delete, or test. |
organization_id | object | — | Clerk organization id (org_...) to link to this connection. |
clerk_instance_id | object | — | Clerk instance id (ins_...) from clerk.get_connected_accounts. Omit to use the default connected account. |
custom_attributes | object | — | Updated custom attribute mappings. |
sync_user_attributes | object | — | Whether to sync user attributes on each sign-in. |
allow_organization_account_linking | object | — | Whether account linking via organization membership is allowed. |
disable_additional_identifications | object | — | Whether to block additional identifications for this connection. |
Parameters from the server's own tool schema.
Why clerk.update_enterprise_connection is rated Medium
Modifies authentication infrastructure with potential impact on user access and security posture across applications.
From the tool's definition Update an enterprise SSO connection in a connected Clerk application.
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs clerk.update_enterprise_connection 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_enterprise_connection, this is the rule to start with:
clerk.update_enterprise_connection 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.update_enterprise_connection call is checked against it from then on.
Questions about clerk.update_enterprise_connection
Update an enterprise SSO connection 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 the updated enterprise_connection summary. 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.update_enterprise_connection accepts 12 parameters: name, oidc, saml, active, domains, connection_id, organization_id, clerk_instance_id, custom_attributes, sync_user_attributes, allow_organization_account_linking, disable_additional_identifications. Required: connection_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.update_enterprise_connection: 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.update_enterprise_connection 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.update_enterprise_connection 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.update_enterprise_connection. 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.update_enterprise_connection 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