jwt_decoder
Decode a JSON Web Token's header and payload (base64url). Does NOT verify the signature — that needs the secret/key. Runs on smart-tools.xyz.
This record as markdown: /tools/io-github-9thshini-smart-tools/jwt-decoder.md
What jwt_decoder does on SmartTools
AI agents invoke jwt_decoder to trigger actions in SmartTools. 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 |
|---|---|---|---|
token | string | Yes | The JWT (header.payload.signature) |
locale | string | — | Language for the source_url link (default en) |
Parameters from the server's own tool schema.
Why jwt_decoder is rated High
jwt_decoder triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsHandles credentials or secrets (token)
Attacks that exploit this kind of access
The rule that runs jwt_decoder safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SmartTools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For jwt_decoder, this is the rule to start with:
jwt_decoder 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 SmartTools, apply this rule, and every jwt_decoder call is checked against it from then on.
Questions about jwt_decoder
Decode a JSON Web Token's header and payload (base64url). Does NOT verify the signature — that needs the secret/key. Runs on smart-tools.xyz. It is categorised as a Execute tool in the SmartTools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
jwt_decoder accepts 2 parameters: token, locale. Required: token. The full parameter table on this page comes from the server's own tool schema.
Register the SmartTools MCP server in PolicyLayer and add a rule for jwt_decoder: 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 SmartTools. Nothing to install.
jwt_decoder 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 jwt_decoder 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 jwt_decoder. 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.
jwt_decoder is provided by the SmartTools MCP server (https://smart-tools.xyz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SmartTools, and thousands of servers like it.
Across the catalogue