AI agents use update-note to create or update resources in MCP Notes Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Notes Server environment.
This tool creates or modifies data in a reversible manner. Updates can typically be undone by applying different updates or restoring from backups, which distinguishes it from the Destructive category. The blast radius is moderate—a misused update-note could corrupt or alter notes, but the effects are not permanent without additional destructive operations.
From the tool's definition Tool name 'update-note' and description 'Update an existing note' indicate modification of existing data. The server description confirms CRUD operations including updates.
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 MCP Notes 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 an existing note. It is categorised as a Write tool in the MCP Notes Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Notes 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 MCP Notes 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 MCP Notes Server MCP server (truaxki/mcp-notes). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Notes 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.
4 MCP Notes Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.