lookup_jwt_decode
Decode a JWT (header + claims, no verify). Pass ?token=... as query. Use for auth-debug agents. Example call: {"query_string": "token=eyJhbGci..."} Cost: $0.005–$0.05 USDC on Base per call.
This record as markdown: /tools/io-github-colinhughes2121-gocreative-agent-api/lookup-jwt-decode.md
What lookup_jwt_decode does on GoCreative Agent API
AI agents call lookup_jwt_decode to retrieve information from GoCreative Agent API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query_string | string | — |
Parameters from the server's own tool schema.
Why lookup_jwt_decode is rated Low
This tool decodes JWT tokens to extract and inspect their header and claims. The description explicitly states it performs no verification and is intended for debugging. Decoding a JWT is a read-only operation that parses the token structure without modifying data, triggering external actions, or causing side effects. It retrieves information from an already-provided token.
From the tool's definition Decode a JWT (header + claims, no verify). Pass ?token=... as query. Use for auth-debug agents.
Attacks that exploit this kind of access
The rule that runs lookup_jwt_decode safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GoCreative Agent API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lookup_jwt_decode, this is the rule to start with:
lookup_jwt_decode is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GoCreative Agent API, apply this rule, and every lookup_jwt_decode call is checked against it from then on.
Questions about lookup_jwt_decode
Decode a JWT (header + claims, no verify). Pass ?token=... as query. Use for auth-debug agents. Example call: {"query_string": "token=eyJhbGci..."} Cost: $0.005–$0.05 USDC on Base per call. It is categorised as a Read tool in the GoCreative Agent API MCP Server, which means it retrieves data without modifying state.
lookup_jwt_decode accepts 1 parameter: query_string. The full parameter table on this page comes from the server's own tool schema.
Register the GoCreative Agent API MCP server in PolicyLayer and add a rule for lookup_jwt_decode: 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 GoCreative Agent API. Nothing to install.
lookup_jwt_decode is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the lookup_jwt_decode 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 lookup_jwt_decode. 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.
lookup_jwt_decode is provided by the GoCreative Agent API MCP server (https://api.gocreativeai.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GoCreative Agent API, and thousands of servers like it.
This server
Across the catalogue