update_external_account

Update a connected account (label/color/unified toggle, or new credentials/host — a connection change is re-tested). Requires TREKMAIL_ALLOW_DESTRUCTIVE=true.

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-external-account.md

WHAT IT DOES

What update_external_account does on TrekMail MCP Server

AI agents use update_external_account 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_external_account is rated Medium

This tool modifies account configuration and credentials reversibly. While updating credentials and host information carries elevated risk (could redirect communications, alter account access), the changes are not inherently destructive or irreversible—credentials and settings can be re-updated.

From the tool's definition Tool description explicitly states it 'Update[s] a connected account' with capabilities to modify 'label/color/unified toggle, or new credentials/host'.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_external_account Rate-limited

update_external_account 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_external_account": {
      "limits": [
        {
          "counter": "update_external_account_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_external_account call is checked against it from then on.

FAQ

Questions about update_external_account

What does the update_external_account tool do? +

Update a connected account (label/color/unified toggle, or new credentials/host — a connection change is re-tested). Requires TREKMAIL_ALLOW_DESTRUCTIVE=true. 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_external_account? +

Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for update_external_account: 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_external_account? +

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

Can I rate-limit update_external_account? +

Yes. Add a rate_limit block to the update_external_account 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_external_account completely? +

Set action: deny in the PolicyLayer policy for update_external_account. 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_external_account? +

update_external_account 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 →