update_domain_note · TrekMail MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_domain_note does on TrekMail MCP Server

AI agents use update_domain_note 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_domain_note needs a policy

This tool creates or modifies domain metadata (notes/descriptions) in a reversible manner. It does not delete data irreversibly, execute code, move money, or trigger external operations. The blast radius of misuse is minimal since updating domain notes cannot corrupt infrastructure or cause service disruption. Classified as Write rather than Read because it performs a modification operation, not just retrieval.

From the tool's definition Tool description states 'Update the note/description on a domain' - this modifies metadata on an existing domain resource. The ability to pass null to clear the field confirms reversible modification capability.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_domain_note Rate-limited

update_domain_note 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_domain_note": {
      "limits": [
        {
          "counter": "update_domain_note_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_domain_note

What does the update_domain_note tool do? +

Update the note/description on a domain (max 120 characters). Pass null to clear. 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_domain_note? +

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

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

Can I rate-limit update_domain_note? +

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

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

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