clerk.update_jwt_template
Update an existing JWT template 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 template summary. Cost = 8 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/clerk.update-jwt-template.md
What clerk.update_jwt_template does on Vee3
AI agents use clerk.update_jwt_template 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 | — | Optional new unique template name. |
claims | object | — | Optional new JWT claims template as a JSON object. |
lifetime | object | — | Optional new token lifetime in seconds (30–315360000). |
signing_key | object | — | Optional custom signing private key. |
template_id | string | Yes | Clerk JWT template id (jtmp_...) to retrieve, update, or delete. |
clerk_instance_id | object | — | Clerk instance id (ins_...) from clerk.get_connected_accounts. Omit to use the default connected account. |
signing_algorithm | object | — | Optional custom signing algorithm. |
allowed_clock_skew | object | — | Optional new allowed clock skew in seconds (0–300). |
custom_signing_key | object | — | Optional flag to enable or disable a custom signing key. |
Parameters from the server's own tool schema.
Why clerk.update_jwt_template is rated Medium
Modifies JWT template configuration reversibly; affects authentication tokens but does not delete or execute arbitrary code directly.
From the tool's definition Update an existing JWT template in a connected Clerk application.
Attacks that exploit this kind of access
The rule that runs clerk.update_jwt_template 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_jwt_template, this is the rule to start with:
clerk.update_jwt_template 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_jwt_template call is checked against it from then on.
Questions about clerk.update_jwt_template
Update an existing JWT template 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 template 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_jwt_template accepts 9 parameters: name, claims, lifetime, signing_key, template_id, clerk_instance_id, signing_algorithm, allowed_clock_skew, custom_signing_key. Required: template_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_jwt_template: 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_jwt_template 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_jwt_template 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_jwt_template. 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_jwt_template 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