update_private_note_settings
Change Private Notes availability, maximum expiry, verified self-receipt availability and the branded public creation page for the authorized account or domain. Setting public_tool_enabled=true makes the creation page available to public visitors on an active White Label host; false hides it. Rec...
This record as markdown: /tools/trekmail-mcp-server/update-private-note-settings.md
What update_private_note_settings does on TrekMail MCP Server
AI agents use update_private_note_settings 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_settings is rated Medium
Modifies account/domain configuration settings reversibly; no deletion or financial impact.
From the tool's definition Change Private Notes availability, public creation page, receipt availability settings
Attacks that exploit this kind of access
The rule that runs update_private_note_settings 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_settings, this is the rule to start with:
update_private_note_settings 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_settings call is checked against it from then on.
Questions about update_private_note_settings
Change Private Notes availability, maximum expiry, verified self-receipt availability and the branded public creation page for the authorized account or domain. Setting public_tool_enabled=true makes the creation page available to public visitors on an active White Label host; false hides it. Receipts allow verified creators to request future email notifications; this call does not send an email. Confirm changes to public access or receipt availability. Omitted fields are unchanged. Requires private-notes:settings:write. Enabling Private Notes alone does not publish the creation page. 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_settings: 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_settings 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_settings 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_settings. 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_settings 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