clerk.create_enterprise_connection_test_run
Start an SSO test flow for an enterprise 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 a short-lived url that opens the IdP test flow. Cost = 8 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/clerk.create-enterprise-connection-test-run.md
What clerk.create_enterprise_connection_test_run does on Vee3
AI agents invoke clerk.create_enterprise_connection_test_run to trigger actions in Vee3. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
connection_id | string | Yes | Clerk enterprise connection id (entc_...) to retrieve, update, delete, or test. |
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.create_enterprise_connection_test_run is rated High
Triggers an external SSO/IdP test flow, initiating an active authentication process.
From the tool's definition Start an SSO test flow for an enterprise connection
Attacks that exploit this kind of access
The rule that runs clerk.create_enterprise_connection_test_run 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_test_run, this is the rule to start with:
clerk.create_enterprise_connection_test_run stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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.create_enterprise_connection_test_run call is checked against it from then on.
Questions about clerk.create_enterprise_connection_test_run
Start an SSO test flow for an enterprise 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 a short-lived url that opens the IdP test flow. Cost = 8 tokens. It is categorised as a Execute tool in the Vee3 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
clerk.create_enterprise_connection_test_run accepts 2 parameters: connection_id, clerk_instance_id. 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.create_enterprise_connection_test_run: 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.create_enterprise_connection_test_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the clerk.create_enterprise_connection_test_run 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.create_enterprise_connection_test_run. 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.create_enterprise_connection_test_run 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