Create a send-from identity. Email must be the mailbox address or one of its aliases.
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.
This tool creates a new email identity that grants additional send-from capabilities. While the action is reversible (identities can typically be deleted), it modifies the email infrastructure by adding new sending personas and could be misused to impersonate legitimate senders or escalate email capabilities if an agent creates unauthorized identities.
From the tool's definition Tool name 'create_identity' with description 'Create a send-from identity' indicates irreversible creation of new email sending capabilities within the infrastructure.
Attacks that exploit this kind of access
Create a send-from identity. Email must be the mailbox address or one of its aliases. 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.
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 →