sendFamilyRequestEmailWithId
Sends out an email to a parent that they need to register and create a family or need to log in and add a child to their existing family.
This record as markdown: /tools/io-fusionauth-mcp-api/sendfamilyrequestemailwithid.md
What sendFamilyRequestEmailWithId does on Fusionauth
AI agents use sendFamilyRequestEmailWithId 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 sendFamilyRequestEmailWithId is rated Medium
This tool triggers an external email communication action. It creates a side effect (sending an email) but does not delete data or move money. Sending an email is a Write/Execute boundary case, but since it is a one-time notification dispatch rather than running arbitrary code, Write is most appropriate. Misuse could lead to spam or phishing-like scenarios, hence medium severity.
From the tool's definition Sends out an email to a parent that they need to register and create a family or need to log in and add a child to their existing family.
Attacks that exploit this kind of access
The rule that runs sendFamilyRequestEmailWithId 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 sendFamilyRequestEmailWithId, this is the rule to start with:
sendFamilyRequestEmailWithId 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 sendFamilyRequestEmailWithId call is checked against it from then on.
Questions about sendFamilyRequestEmailWithId
Sends out an email to a parent that they need to register and create a family or need to log in and add a child to their existing family. 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 sendFamilyRequestEmailWithId: 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.
sendFamilyRequestEmailWithId 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 sendFamilyRequestEmailWithId 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 sendFamilyRequestEmailWithId. 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.
sendFamilyRequestEmailWithId 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