create_referral_invites
Step 2 of the colleague-invite flow. Given the recipients the user PICKED, records each invite and returns a UNIQUE referral link per person (so the user can later see who installed/activated). Call this AFTER the user chooses, then put each returned link into that person's email and send via sen...
This record as markdown: /tools/com-local-mcp-local-mcp/create-referral-invites.md
What create_referral_invites does on Local
AI agents use create_referral_invites to create or update resources in Local, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
lang | string | — | ISO language of the invite you're writing (the user's conversation language, e.g. 'es', 'en'). Defaults to the Mac's language. |
recipients | array | Yes | The picked recipients. |
Parameters from the server's own tool schema.
Why create_referral_invites is rated Medium
This tool performs a data creation/modification operation—it records invitation data and generates unique referral links. This is a Write operation (reversible state change). Severity is medium because misuse could result in spam invites or fraudulent referral links sent to unintended recipients, but the tool itself does not execute external actions, delete data, or move money.
From the tool's definition Creates referral invite records with unique links per recipient ('records each invite and returns a UNIQUE referral link per person'). The tool modifies state by storing invite data, though it does not send emails itself ('Does NOT send anything itself').
Attacks that exploit this kind of access
The rule that runs create_referral_invites safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_referral_invites, this is the rule to start with:
create_referral_invites 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 Local, apply this rule, and every create_referral_invites call is checked against it from then on.
Questions about create_referral_invites
Step 2 of the colleague-invite flow. Given the recipients the user PICKED, records each invite and returns a UNIQUE referral link per person (so the user can later see who installed/activated). Call this AFTER the user chooses, then put each returned link into that person's email and send via send_email. Does NOT send anything itself. Pass lang = the language you're actually writing the invite in (the user's conversation language, e.g. "es", "en") — it's recorded with the invite. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_referral_invites accepts 2 parameters: lang, recipients. Required: recipients. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for create_referral_invites: 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 Local. Nothing to install.
create_referral_invites 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 create_referral_invites 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 create_referral_invites. 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.
create_referral_invites is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue