create_identity
Configure an existing mailbox/alias persona, or create a Send As identity. Pass external_account_id when you read that address
This record as markdown: /tools/trekmail-mcp-server/create-identity.md
What create_identity does on TrekMail MCP Server
AI agents use create_identity 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_identity is rated Medium
Creates or modifies email identities reversibly, affecting sender personas and mailbox configurations.
From the tool's definition create/configure mailbox/alias persona, Send As identity
Attacks that exploit this kind of access
The rule that runs create_identity 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_identity, this is the rule to start with:
create_identity 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_identity call is checked against it from then on.
Questions about create_identity
Configure an existing mailbox/alias persona, or create a Send As identity. Pass external_account_id when you read that address. 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_identity: 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_identity 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_identity 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_identity. 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_identity 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