update_note
Replace the entire body of an existing note. WARNING: This overwrites all content. Read the note first if you need to preserve parts of it. Attachments may be lost.
This record as markdown: /tools/io-github-heznpc-iconnect/update-note.md
What update_note does on Iconnect
AI agents use update_note to create or update resources in Iconnect, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Iconnect environment.
Why update_note is rated Medium
The tool modifies existing data by overwriting the full content of a note, which is reversible in principle (the note still exists), but the warning about attachments being lost introduces a partially destructive element.
From the tool's definition 'Replace the entire body of an existing note. WARNING: This overwrites all content. Attachments may be lost.'
Risk signalsBulk/mass operation — affects multiple targets
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 Iconnect, 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 Iconnect, apply this rule, and every update_note call is checked against it from then on.
Questions about update_note
Replace the entire body of an existing note. WARNING: This overwrites all content. Read the note first if you need to preserve parts of it. Attachments may be lost. It is categorised as a Write tool in the Iconnect MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Iconnect 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 Iconnect. 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 Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue