Import contacts from a base64-encoded CSV or VCF file (max 2 MB).
AI agents use import_contacts 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.
Importing contacts creates or adds data to the system. This is a Write operation because it modifies the contact database by adding new records. The operation is reversible since imported contacts can be individually or bulk deleted.
From the tool's definition Tool description states it imports contacts, which creates new contact records in the system from an uploaded file. The action is reversible (contacts can be deleted), making it Write rather than Destructive.
Attacks that exploit this kind of access
Import contacts from a base64-encoded CSV or VCF file (max 2 MB). 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 import_contacts: 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.
import_contacts 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 import_contacts 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 import_contacts. 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.
import_contacts 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 →