update_private_note
Edit your reference, opening confirmation or verified self-receipt, or shorten expiry. Requires the latest revision. Text, password and read policy are immutable: encrypt/create a new note and explicitly revoke the old one to replace them. Never returns secret text.
This record as markdown: /tools/trekmail-mcp-server/update-private-note.md
What update_private_note does on TrekMail MCP Server
AI agents use update_private_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 update_private_note is rated Medium
Modifies private note metadata reversibly; requires revision handling indicating controlled updates without data loss.
From the tool's definition Edit your reference, opening confirmation or verified self-receipt, or shorten expiry.
Attacks that exploit this kind of access
The rule that runs update_private_note 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_private_note, this is the rule to start with:
update_private_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.
The button opens the PolicyLayer dashboard: create your workspace, connect TrekMail MCP Server, apply this rule, and every update_private_note call is checked against it from then on.
Questions about update_private_note
Edit your reference, opening confirmation or verified self-receipt, or shorten expiry. Requires the latest revision. Text, password and read policy are immutable: encrypt/create a new note and explicitly revoke the old one to replace them. Never returns secret text. 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.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for update_private_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.
update_private_note is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_private_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.
Set action: deny in the PolicyLayer policy for update_private_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.
update_private_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.
More on TrekMail MCP Server, and thousands of servers like it.
This server
Across the catalogue