create_message_token
Create a message API token for a mailbox. The token grants access to read, write, or send messages for that mailbox. The plain token is returned only once.
This record as markdown: /tools/trekmail-mcp-server/create-message-token.md
What create_message_token does on TrekMail MCP Server
AI agents use create_message_token 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_message_token is rated Medium
This tool creates authentication credentials that persist and grant ongoing access to mailbox operations. While the immediate action is creating a token (Write), the token's grants span Read, Write, and Execute (send) capabilities. However, the tool itself performs a Write action—creating a new credential object.
From the tool's definition Tool description states it 'Create[s] a message API token' and 'grants access to read, write, or send messages'. The act of creating a token is a Write operation (creates a credential artifact).
Attacks that exploit this kind of access
The rule that runs create_message_token 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_message_token, this is the rule to start with:
create_message_token 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_message_token call is checked against it from then on.
Questions about create_message_token
Create a message API token for a mailbox. The token grants access to read, write, or send messages for that mailbox. The plain token is returned only once. 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_message_token: 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_message_token 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_message_token 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_message_token. 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_message_token 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