clerk.create_api_key

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

Medium RISK CLASS

Category Write

Parameters 92 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-api-key.md

WHAT IT DOES

What clerk.create_api_key does on Vee3

AI agents use clerk.create_api_key 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	Human-readable name for the new API key.
`claims`	object	—	Custom claims to embed in tokens minted from this API key.
`scopes`	object	—	Permission scopes to grant the API key.
`subject`	string	Yes	Subject the API key is scoped to (user_... or org_...).
`key_type`	object	—	API key type (typically "api_key").
`created_by`	object	—	User id to record as the creator of this API key.
`description`	object	—	Optional description for the API key.
`clerk_instance_id`	object	—	Clerk instance id (ins_...) from clerk.get_connected_accounts. Omit to use the default connected account.
`seconds_until_expiration`	object	—	Seconds from creation until the API key expires.

Parameters from the server's own tool schema.

RISK

Why clerk.create_api_key is rated Medium

Creates new authentication credentials enabling persistent access to Clerk systems with elevated privileges.

From the tool's definition Create an API key in a connected Clerk application. Returned secret is high-privilege credential.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

clerk.create_api_key Rate-limited

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

FAQ

Questions about clerk.create_api_key

What does the clerk.create_api_key tool do? +

Create an API key in a connected Clerk application. Sensitive — the returned secret is a high-privilege credential; do not log or expose it. 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 API key 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_api_key accept? +

clerk.create_api_key accepts 9 parameters: name, claims, scopes, subject, key_type, created_by, description, clerk_instance_id, seconds_until_expiration. Required: name, subject. The full parameter table on this page comes from the server's own tool schema.

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

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

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

Can I rate-limit clerk.create_api_key? +

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

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

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