sendPasswordlessCodeWithId
Send a passwordless authentication code in an email to complete login.
This record as markdown: /tools/io-fusionauth-mcp-api/sendpasswordlesscodewithid.md
What sendPasswordlessCodeWithId does on Fusionauth
AI agents use sendPasswordlessCodeWithId 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 sendPasswordlessCodeWithId is rated Medium
While the tool doesn't directly create or modify user data structures, it initiates an email delivery and generates a temporary authentication credential, which constitutes a reversible state change. This is Write rather than Execute because the operation is well-defined (send passwordless code) and not arbitrary code execution. It's not Read because it has side effects.
From the tool's definition Tool performs a passwordless code generation and send operation (e.g., 'Send a passwordless authentication code in an email'). This modifies state by creating a new authentication code and triggers an email delivery action with side effects.
Attacks that exploit this kind of access
The rule that runs sendPasswordlessCodeWithId 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 sendPasswordlessCodeWithId, this is the rule to start with:
sendPasswordlessCodeWithId 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 sendPasswordlessCodeWithId call is checked against it from then on.
Questions about sendPasswordlessCodeWithId
Send a passwordless authentication code in an email to complete login. 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 sendPasswordlessCodeWithId: 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.
sendPasswordlessCodeWithId 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 sendPasswordlessCodeWithId 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 sendPasswordlessCodeWithId. 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.
sendPasswordlessCodeWithId 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