This record as markdown: /tools/io-fusionauth-mcp-api/vendjwtwithid.md
What vendJWTWithId does on Fusionauth
AI agents use vendJWTWithId to create or update resources in Fusionauth, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fusionauth environment.
Why vendJWTWithId is rated Medium
Vending (issuing) JWTs creates new authentication tokens that can be used to access protected resources. This is fundamentally a write operation that creates security artifacts. While not destructive or financial, issuance of JWT tokens by an AI agent without proper authorization could grant unintended access to systems or users, posing a high severity risk.
From the tool's definition Tool name 'vendJWTWithId' indicates issuing/creating JWT tokens. The description 'It' is uninformative and truncated, which lowers confidence. JWT issuance is a write operation that creates authentication credentials with potential side effects if misused.
Attacks that exploit this kind of access
The rule that runs vendJWTWithId 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 vendJWTWithId, this is the rule to start with:
vendJWTWithId 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 Fusionauth, apply this rule, and every vendJWTWithId call is checked against it from then on.
Questions about vendJWTWithId
It. It is categorised as a Write tool in the Fusionauth MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fusionauth MCP server in PolicyLayer and add a rule for vendJWTWithId: 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.
vendJWTWithId 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 vendJWTWithId 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 vendJWTWithId. 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.
vendJWTWithId 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.
This server
Across the catalogue