AI agents use remnote_update_tags 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.
The tool modifies note attributes (tags) but does not delete data or execute arbitrary code. Adding or removing tags is a write operation that can be undone by adding/removing tags again. The use of 'exact tag Rem IDs' reduces risk of accidental misapplication. Severity is medium because bulk or incorrect tag changes could affect note organization and searchability, but the impact is localized and reversible.
From the tool's definition Tool description states 'Add or remove tags from a note' — these are reversible modifications to note metadata.
Attacks that exploit this kind of access
Add or remove tags from a note by exact tag Rem IDs. Use this for production tagging workflows to avoid ambiguous name lookup. 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_tags: 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_tags 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_tags 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_tags. 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_tags 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 →