AI agents use update_notebook 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.
This tool modifies notebook metadata or properties reversibly. It is not destructive (no deletion or permanent overwrites) and does not execute arbitrary code or move financial assets. The medium severity reflects that updating a notebook could affect multiple notes and collaborative access, but changes are reversible via subsequent updates.
From the tool's definition Tool name 'update_notebook' and description 'Update an existing notebook' indicate modification of existing data. Server description confirms 'note operations (create, read, update, delete)'.
Documented attack patterns abuse exactly the kind of access update_notebook 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_notebook:
{
"version": "1",
"default": "deny",
"tools": {
"update_notebook": {
"limits": [
{
"counter": "update_notebook_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_notebook 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 an existing notebook. 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_notebook: 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_notebook 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_notebook 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_notebook. 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_notebook 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.