Medium Risk

vendJWTWithId

It's a JWT vending machine! Issue a new access token (JWT) with the provided claims in the request. This JWT is not scoped to a tenant or user, it is a free form token that will contain what claims you provide. <p> The iat, exp and jti claims will be added by FusionAuth, all other claims must b...

Part of the Mcp Api MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@fusionauth/mcp-api Write Risk 2/5

AI agents use vendJWTWithId to create or modify resources in Mcp Api. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call vendJWTWithId repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Mcp Api.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-fusionauth-mcp-api.yaml
tools:
  vendJWTWithId:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Mcp Api policy for all 310 tools.

Tool Name vendJWTWithId
Category Write
MCP Server Mcp Api MCP Server
Risk Level Medium

View all 310 tools →

What does the vendJWTWithId tool do? +

It's a JWT vending machine! Issue a new access token (JWT) with the provided claims in the request. This JWT is not scoped to a tenant or user, it is a free form token that will contain what claims you provide. <p> The iat, exp and jti claims will be added by FusionAuth, all other claims must be provided by the caller. If a TTL is not provided in the request, the TTL will be retrieved from the default Tenant or the Tenant specified on the request either by way of the X-FusionAuth-TenantId request header, or a tenant scoped API key.. It is categorised as a Write tool in the Mcp Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on vendJWTWithId? +

Add a rule in your Intercept YAML policy under the tools section for vendJWTWithId. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Api MCP server.

What risk level is vendJWTWithId? +

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

Can I rate-limit vendJWTWithId? +

Yes. Add a rate_limit block to the vendJWTWithId rule in your Intercept 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 vendJWTWithId completely? +

Set action: deny in the Intercept 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.

What MCP server provides vendJWTWithId? +

vendJWTWithId is provided by the Mcp Api MCP server (@fusionauth/mcp-api). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Mcp Api

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.