update_identity

SERVERTrekMail MCP Server SOURCEtrekmail/mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/trekmail-mcp-server/update-identity.md

WHAT IT DOES

What update_identity does on TrekMail MCP Server

AI agents use update_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.

RISK

Why update_identity is rated Medium

Modifies email identity configuration reversibly; potential for spoofing/impersonation if misused against connected accounts.

From the tool's definition Update name, reply-to, signature, default status, SMTP route

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_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 update_identity, this is the rule to start with:

update_identity Rate-limited

update_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_identity": {
      "limits": [
        {
          "counter": "update_identity_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TrekMail MCP Server, apply this rule, and every update_identity call is checked against it from then on.

FAQ

Questions about update_identity

What does the update_identity tool do? +

Update name, reply-to, signature, default status, or SMTP route. When updating a connected-inbox Send As identity, pass its external_account_id so the API can enforce the exact source binding. Requires scope: messages:write. 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.

How do I enforce a policy on update_identity? +

Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_identity? +

update_identity is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_identity? +

Yes. Add a rate_limit block to the update_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.

How do I block update_identity completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_identity? +

update_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.

KEEP EXPLORING

More on TrekMail MCP Server, and thousands of servers like it.

This server

All 248 TrekMail MCP Server tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →