resend_white_label_invitation
Replace a pending member
This record as markdown: /tools/trekmail-mcp-server/resend-white-label-invitation.md
What resend_white_label_invitation does on TrekMail MCP Server
AI agents use resend_white_label_invitation 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 resend_white_label_invitation is rated Medium
Modifies pending member status reversibly; moderate scope affecting account membership and white-label setup.
From the tool's definition Replace a pending member; white_label invitation management
Attacks that exploit this kind of access
The rule that runs resend_white_label_invitation 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 resend_white_label_invitation, this is the rule to start with:
resend_white_label_invitation 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 resend_white_label_invitation call is checked against it from then on.
Questions about resend_white_label_invitation
Replace a pending member. 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 resend_white_label_invitation: 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.
resend_white_label_invitation 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 resend_white_label_invitation 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 resend_white_label_invitation. 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.
resend_white_label_invitation 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