Update the content of an existing note
AI agents use update_note to create or update resources in macOS MCP Servers — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your macOS MCP Servers environment.
This tool modifies existing notes, which constitutes a Write action. The severity is medium because while the change is reversible (can be undone), it affects user-created content and an AI agent with access could maliciously alter important notes.
From the tool's definition Tool name is 'update_note' and description states 'Update the content of an existing note' — this is a modification operation on user data that is reversible.
Attacks that exploit this kind of access
Update the content of an existing note. It is categorised as a Write tool in the macOS MCP Servers MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the macOS MCP Servers 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 macOS MCP Servers. 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 macOS MCP Servers MCP server (tdisawas0github/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →