issueJWTWithId
Issue a new access token (JWT) for the requested Application after ensuring the provided JWT is valid. A valid access token is properly signed and not expired. <p> This API may be used in an SSO configuration to issue new tokens for another application after the user has obtained a valid token fr...
This record as markdown: /tools/io-fusionauth-mcp-api/issuejwtwithid.md
What issueJWTWithId does on Fusionauth
AI agents invoke issueJWTWithId to trigger actions in Fusionauth. 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.
Why issueJWTWithId is rated High
This tool issues authentication tokens (JWTs) which grant access to applications. While it is a token generation operation rather than a data write or delete, it triggers an external security operation with significant blast radius — a misused or forged JWT issuance can grant unauthorized access to any application in the SSO ecosystem.
From the tool's definition Issue a new access token (JWT) for the requested Application after ensuring the provided JWT is valid... issue new tokens for another application after the user has obtained a valid token from authentication.
Attacks that exploit this kind of access
The rule that runs issueJWTWithId safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fusionauth, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For issueJWTWithId, this is the rule to start with:
issueJWTWithId 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 Fusionauth, apply this rule, and every issueJWTWithId call is checked against it from then on.
Questions about issueJWTWithId
Issue a new access token (JWT) for the requested Application after ensuring the provided JWT is valid. A valid access token is properly signed and not expired. <p> This API may be used in an SSO configuration to issue new tokens for another application after the user has obtained a valid token from authentication. It is categorised as a Execute tool in the Fusionauth MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Fusionauth MCP server in PolicyLayer and add a rule for issueJWTWithId: 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 Fusionauth. Nothing to install.
issueJWTWithId 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 issueJWTWithId 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 issueJWTWithId. 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.
issueJWTWithId is provided by the Fusionauth MCP server (@fusionauth/mcp-api). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fusionauth, and thousands of servers like it.
Across the catalogue