New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

clerk.list_enterprise_connection_test_runs

List SAML or OIDC debug test runs for an enterprise SSO connection. Call clerk.get_connected_accounts first. Pass clerk_instance_id to target a specific connection, or omit it to use the default account. Returns test_runs summaries plus total_count. Cost = 5 tokens.

SERVERVee3 SOURCEhttps://mcp.vee3.io/mcp
Low RISK CLASS
Category Read
Parameters 51 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vee3io-vee3/clerk.list-enterprise-connection-test-runs.md

What clerk.list_enterprise_connection_test_runs does on Vee3

AI agents call clerk.list_enterprise_connection_test_runs to retrieve information from Vee3 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
limit object Maximum number of results to return (1–500).
offset object Number of results to skip before returning.
status object Filter by test run status: "pending", "success", or "failed".
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.list_enterprise_connection_test_runs is rated Low

Retrieves debug test run summaries without modifying or deleting data, with no side effects.

From the tool's definition List SAML or OIDC debug test runs for an enterprise SSO connection

Questions about clerk.list_enterprise_connection_test_runs

What does the clerk.list_enterprise_connection_test_runs tool do? +

List SAML or OIDC debug test runs for an enterprise SSO connection. Call clerk.get_connected_accounts first. Pass clerk_instance_id to target a specific connection, or omit it to use the default account. Returns test_runs summaries plus total_count. Cost = 5 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.

What parameters does clerk.list_enterprise_connection_test_runs accept? +

clerk.list_enterprise_connection_test_runs accepts 5 parameters: limit, offset, status, connection_id, clerk_instance_id. Required: connection_id. The full parameter table on this page comes from the server's own tool schema.

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

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

clerk.list_enterprise_connection_test_runs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit clerk.list_enterprise_connection_test_runs? +

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

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

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

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Vee3's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.