identities_update · Mailgent MCP Server MCP: Risk & Policy

WHAT IT DOES

What identities_update does on Mailgent MCP Server

AI agents use identities_update to create or update resources in Mailgent MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mailgent MCP Server environment.

WHY IT NEEDS A POLICY

Why identities_update needs a policy

This tool creates or modifies data (identity display names) in a reversible manner. It does not execute code, delete data, or move money. The blast radius is medium because a compromised agent could alter identity metadata to impersonate users or create confusion in email communications, but the underlying email address cannot be changed and modifications could be reverted.

From the tool's definition Tool description states it can 'Rename an identity' and modify the 'display name'. The immutability of the inbox email address suggests reversible modification of identity attributes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

identities_update Rate-limited

identities_update 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": {
    "identities_update": {
      "limits": [
        {
          "counter": "identities_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mailgent MCP Server, so you can run agents against it safely.

FAQ

Questions about identities_update

What does the identities_update tool do? +

Rename an identity. The inbox email address is immutable; only the display name can change. For scope changes, use identities_update_scopes. It is categorised as a Write tool in the Mailgent 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 identities_update? +

Register the Mailgent MCP Server MCP server in PolicyLayer and add a rule for identities_update: 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 Mailgent MCP Server. Nothing to install.

What risk level is identities_update? +

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

Can I rate-limit identities_update? +

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

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

identities_update is provided by the Mailgent MCP Server MCP server (loomal-ai/loomal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.