update_note
Updates an existing note in Apple Notes. Change the title and/or body (the body accepts Markdown, converted to Apple Notes' native formatting). Find note_id with list_notes or search_notes. Requires confirm=true.
This record as markdown: /tools/com-local-mcp-local-mcp/update-note.md
What update_note does on Local
AI agents use update_note to create or update resources in Local, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | string | — | |
title | string | — | |
confirm | boolean | — | |
note_id | string | — | |
note_name | string | — |
Parameters from the server's own tool schema.
Why update_note is rated Medium
This tool creates or modifies data (Apple Notes content) in a reversible manner. While updates are not destructive and data remains intact and recoverable, the tool can alter user information. The confirm=true requirement provides a safeguard against accidental invocation.
From the tool's definition Tool description explicitly states 'Updates an existing note' and 'Change the title and/or body', indicating reversible modification of data. Requires confirm=true safeguard.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs update_note safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_note, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every update_note call is checked against it from then on.
Questions about update_note
Updates an existing note in Apple Notes. Change the title and/or body (the body accepts Markdown, converted to Apple Notes' native formatting). Find note_id with list_notes or search_notes. Requires confirm=true. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_note accepts 5 parameters: body, title, confirm, note_id, note_name. The full parameter table on this page comes from the server's own tool schema.
Register the Local 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 Local. 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 Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue