jwt_sign

SERVERScorpTech x402 API SOURCEhttps://scorptech.it.com/api/x402/mcp

Medium RISK CLASS

Category Write

Parameters 121 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-it-scorptech-x402/jwt-sign.md

WHAT IT DOES

What jwt_sign does on ScorpTech x402 API

AI agents use jwt_sign to create or update resources in ScorpTech x402 API, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ScorpTech x402 API environment.

Parameter	Type	Required	Description
`alg`	string	—
`iat`	boolean	—	sign: add iat
`jti`	boolean	—	sign: add a random jti (UUID v4)
`now`	integer	—	Unix time to treat as "now" (default: server time)
`mode`	string	—
`token`	string	—	verify: the compact JWT
`claims`	object	—	sign: payload claims (JSON object)
`header`	object	—	sign: extra header fields, e.g. {"kid": "k1"}
`issuer`	string	—
`leeway`	integer	—	verify: clock-skew allowance in seconds
`secret`	string	Yes	HMAC secret (never echoed)
`subject`	string	—

Parameters from the server's own tool schema.

RISK

Why jwt_sign is rated Medium

An AI agent can call jwt_sign faster than any human can review: one bad instruction and it creates or modifies resources in ScorpTech x402 API by the hundred, each call as confident as the last.

Risk signalsHandles credentials or secrets (secret) · High parameter count (16 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs jwt_sign safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For jwt_sign, this is the rule to start with:

jwt_sign Rate-limited

jwt_sign 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": {
    "jwt_sign": {
      "limits": [
        {
          "counter": "jwt_sign_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 ScorpTech x402 API, apply this rule, and every jwt_sign call is checked against it from then on.

FAQ

Questions about jwt_sign

What does the jwt_sign tool do? +

Create or verify HMAC-signed JWTs (HS256 / HS384 / HS512) — for test fixtures, service-to-service tokens, webhook auth and debugging "invalid signature" errors. sign: builds header + claims with iat / exp / nbf from durations ("15m", "1h", "7d"), iss / sub / aud shortcuts and an optional random jti, and returns the compact token. verify: checks the signature in constant time plus exp / nbf / iat with leeway and optional issuer / audience expectations, and explains exactly why a token fails. The secret can be UTF-8, base64, base64url or hex; it is never echoed or stored. Warns when the secret is shorter than the hash (RFC 7518 §3.2). For RS / ES / EdDSA token decoding and JWKS verification use /v1/jwt-decode. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/jwt-sign. It is categorised as a Write tool in the ScorpTech x402 API MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does jwt_sign accept? +

jwt_sign accepts 12 parameters: alg, iat, jti, now, mode, token, claims, header, issuer, leeway, secret, subject. Required: secret. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on jwt_sign? +

Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for jwt_sign: 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 ScorpTech x402 API. Nothing to install.

What risk level is jwt_sign? +

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

Can I rate-limit jwt_sign? +

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

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

jwt_sign is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ScorpTech x402 API, and thousands of servers like it.

This server

All 1012 ScorpTech x402 API tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →