revoke_private_note
Permanently revoke your private note. Requires private-notes:revoke and destructive actions enabled. Does not consume or reveal content.
This record as markdown: /tools/trekmail-mcp-server/revoke-private-note.md
What revoke_private_note does on TrekMail MCP Server
AI agents call revoke_private_note to permanently remove resources in TrekMail MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why revoke_private_note is rated Critical
Irreversibly deletes private note data with no undo capability.
From the tool's definition Permanently revoke your private note. Destructive actions enabled.
Attacks that exploit this kind of access
The rule that runs revoke_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 revoke_private_note, this is the rule to start with:
revoke_private_note is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect TrekMail MCP Server, apply this rule, and every revoke_private_note call is checked against it from then on.
Questions about revoke_private_note
Permanently revoke your private note. Requires private-notes:revoke and destructive actions enabled. Does not consume or reveal content. It is categorised as a Destructive tool in the TrekMail MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for revoke_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.
revoke_private_note is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the revoke_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 revoke_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.
revoke_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.
Across the catalogue