clerk.create_enterprise_connection

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

Medium RISK CLASS

Category Write

Parameters 123 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.create-enterprise-connection.md

WHAT IT DOES

What clerk.create_enterprise_connection does on Vee3

AI agents use clerk.create_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`	string	Yes	Display name for the enterprise connection.
`oidc`	object	—	OIDC client configuration when provider uses OAuth.
`saml`	object	—	SAML IdP configuration when provider uses SAML.
`active`	object	—	Whether the connection is active.
`domains`	array	Yes	Email domains that may use this connection.
`provider`	string	Yes	Identity provider key (for example saml_custom or oidc_custom).
`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	—	Custom attribute mappings from the IdP to user metadata.
`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.

RISK

Why clerk.create_enterprise_connection is rated Medium

Creates reversible authentication infrastructure configuration. High severity due to identity system access implications.

From the tool's definition Create a SAML or OIDC enterprise SSO connection in a connected Clerk application.

Risk signalsHigh parameter count (12 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

clerk.create_enterprise_connection Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "clerk.create_enterprise_connection": {
      "limits": [
        {
          "counter": "clerk.create_enterprise_connection_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.create_enterprise_connection call is checked against it from then on.

FAQ

Questions about clerk.create_enterprise_connection

What does the clerk.create_enterprise_connection tool do? +

Create a SAML or OIDC 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 new enterprise_connection summary. Cost = 10 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.create_enterprise_connection accept? +

clerk.create_enterprise_connection accepts 12 parameters: name, oidc, saml, active, domains, provider, organization_id, clerk_instance_id, custom_attributes, sync_user_attributes, allow_organization_account_linking, disable_additional_identifications. Required: name, domains, provider. The full parameter table on this page comes from the server's own tool schema.

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

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

What risk level is clerk.create_enterprise_connection? +

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

Can I rate-limit clerk.create_enterprise_connection? +

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

How do I block clerk.create_enterprise_connection completely? +

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

What MCP server provides clerk.create_enterprise_connection? +

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

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 →