AI agents call expunge_tag to permanently remove resources in Evernote MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes a tag from Evernote. Although a tag is metadata rather than primary content, its permanent deletion cannot be undone and may impact note organization and searchability across potentially many notes. The blast radius depends on how widely the tag is used, but the action itself is quintessentially destructive: it removes data that cannot be recovered.
From the tool's definition 'Permanently delete a tag' — the verb 'Permanently delete' and the word 'expunge' both indicate irreversible removal of data.
Documented attack patterns abuse exactly the kind of access expunge_tag gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Evernote MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for expunge_tag:
{
"version": "1",
"default": "deny",
"hide": [
"expunge_tag"
]
} expunge_tag disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Permanently delete a tag. It is categorised as a Destructive tool in the Evernote MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Evernote MCP Server MCP server in PolicyLayer and add a rule for expunge_tag: 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 Evernote MCP Server. Nothing to install.
expunge_tag 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 expunge_tag 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 expunge_tag. 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.
expunge_tag is provided by the Evernote MCP Server MCP server (kensou24/evernote-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Evernote MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
52 Evernote MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.