create_invite
Create a setup invite for a mailbox. Sends an email to the recipient with a link to set their own password and complete mailbox setup. Storage defaults to the shared account pool; pass storage_allocation_mb to pre-allocate dedicated storage that the recipient inherits at redeem.
This record as markdown: /tools/trekmail-mcp-server/create-invite.md
What create_invite does on TrekMail MCP Server
AI agents use create_invite to create or update resources in TrekMail MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TrekMail MCP Server environment.
Why create_invite is rated Medium
This tool creates a new invite object and sends an email, both Write operations. The effects are reversible (the invite can be revoked, the mailbox setup incomplete). While it has side effects (email dispatch), it does not execute arbitrary code, delete data, move money, or trigger irreversible changes.
From the tool's definition Tool description states it 'Create[s] a setup invite for a mailbox' and 'Sends an email to the recipient' — these are create and send operations that modify state (mailbox setup, email dispatch) reversibly.
Attacks that exploit this kind of access
The rule that runs create_invite safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TrekMail MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_invite, this is the rule to start with:
create_invite 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 TrekMail MCP Server, apply this rule, and every create_invite call is checked against it from then on.
Questions about create_invite
Create a setup invite for a mailbox. Sends an email to the recipient with a link to set their own password and complete mailbox setup. Storage defaults to the shared account pool; pass storage_allocation_mb to pre-allocate dedicated storage that the recipient inherits at redeem. It is categorised as a Write tool in the TrekMail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for create_invite: 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 TrekMail MCP Server. Nothing to install.
create_invite 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_invite 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_invite. 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_invite is provided by the TrekMail MCP Server MCP server (trekmail/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TrekMail MCP Server, and thousands of servers like it.
This server
Across the catalogue