Create multiple setup invites in a single request. Each item specifies a local_part and recipient_email, and may optionally override the target domain via domain_id (otherwise the batch domain_id is used) — so one call can invite people onto several of your domains. Returns results for each item.
AI agents use create_invites_bulk 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.
This tool creates new invitation records in bulk (Write category) but does not execute arbitrary code, delete data irreversibly, or move money. The blast radius is medium because bulk invitation creation could be misused to spam users or create unauthorized invites across domains if an agent sends invites to unintended recipients or domains, but the action is reversible (invites can typically be revoked or expire).
From the tool's definition Tool description states it 'Create[s] multiple setup invites' and 'Returns results for each item', indicating creation of email invitation records.
Attacks that exploit this kind of access
Create multiple setup invites in a single request. Each item specifies a local_part and recipient_email, and may optionally override the target domain via domain_id (otherwise the batch domain_id is used) — so one call can invite people onto several of your domains. Returns results for each item. 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_invites_bulk: 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_invites_bulk 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_invites_bulk 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_invites_bulk. 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_invites_bulk 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →