AI agents use remnote_update_note to create or update resources in Remnote — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Remnote environment.
This tool modifies existing notes by changing their metadata/titles. Metadata updates are reversible (can be changed back), so this falls under Write rather than Destructive. The severity is medium because changing note titles could disrupt organization and references within a knowledge base, but the effect is non-destructive and limited in scope.
From the tool's definition Tool description states 'Update note metadata in RemNote. Use this tool for title changes only.' The verb 'Update' and the action of modifying metadata (specifically titles) constitute a Write operation—data modification that is reversible.
Attacks that exploit this kind of access
Update note metadata in RemNote. Use this tool for title changes only. It is categorised as a Write tool in the Remnote MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Remnote MCP server in PolicyLayer and add a rule for remnote_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 Remnote. Nothing to install.
remnote_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 remnote_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 remnote_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.
remnote_update_note is provided by the Remnote MCP server (remnote-mcp-server). 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 →