AI agents use removeTagFromNote to create or update resources in Memnote — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Memnote environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Note ID |
tagId | string | Yes | Tag ID |
Parameters from the server's own tool schema.
Removing a tag from a note is a reversible write operation (the tag can be re-added via addTagToNote). It modifies data but does not delete the note or the tag itself, so it falls under Write rather than Destructive. Misuse could cause loss of organization/categorization but is recoverable.
From the tool's definition 'Remove tag from note' — detaches an association between a tag and a note, modifying the note's metadata
Attacks that exploit this kind of access
Remove tag from note. It is categorised as a Write tool in the Memnote MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
removeTagFromNote accepts 2 parameters: id, tagId. Required: id, tagId. The full parameter table on this page comes from the server's own tool schema.
Register the Memnote MCP server in PolicyLayer and add a rule for removeTagFromNote: 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 Memnote. Nothing to install.
removeTagFromNote 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 removeTagFromNote 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 removeTagFromNote. 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.
removeTagFromNote is provided by the Memnote MCP server (@randomfact/memnote-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 →