AI agents use update_note to create or update resources in Evernote MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Evernote MCP Server environment.
update_note modifies note data reversibly (Write category). Severity is high because an AI agent could maliciously alter notes across notebooks, potentially affecting important documents, though this remains reversible unlike destructive operations. The empty description lowers confidence slightly from critical, but the server description and tool name provide clear evidence of its Write capability.
From the tool's definition Tool named 'update_note' with sibling tools including 'delete_note' and 'create_note'. Server description explicitly states 'note operations (create, read, update, delete)'. The tool modifies existing notes reversibly.
Documented attack patterns abuse exactly the kind of access update_note 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 update_note:
{
"version": "1",
"default": "deny",
"tools": {
"update_note": {
"limits": [
{
"counter": "update_note_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_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.
Free to start. No card required.
update_note. It is categorised as a Write tool in the Evernote MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Evernote MCP Server MCP server in PolicyLayer and add a rule for update_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 Evernote MCP Server. Nothing to install.
update_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_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_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_note 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.