update_contact_group · TrekMail MCP Server MCP

WHAT IT DOES

What update_contact_group does on TrekMail MCP Server

AI agents use update_contact_group 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 IT NEEDS A POLICY

Why update_contact_group needs a policy

This tool creates or modifies data reversibly by updating contact group naming information. It does not delete, execute code, move financial assets, or perform irreversible operations. The medium severity reflects that while reversible, unauthorized modifications to contact groups could affect email distribution and organizational communication if misused by an AI agent without proper authorization checks.

From the tool's definition Tool description states 'Rename a contact group' which modifies metadata of an existing contact group. The operation is reversible (can be renamed again to restore original name).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_contact_group Rate-limited

update_contact_group 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_contact_group": {
      "limits": [
        {
          "counter": "update_contact_group_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 TrekMail MCP Server, so you can run agents against it safely.

FAQ

Questions about update_contact_group

What does the update_contact_group tool do? +

Rename a contact group. 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_contact_group? +

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

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

Can I rate-limit update_contact_group? +

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

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

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