AI agents use updateTag 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 | |
body | object | Yes |
Parameters from the server's own tool schema.
This tool creates or modifies data in a reversible manner (update operation on tags). It does not delete data (Destructive), execute code (Execute), move money (Financial), or have side effects beyond data modification. The low severity reflects that tag updates in a note-taking application have minimal blast radius—changes can be reverted and affect only tag metadata, not core note content or system integrity.
From the tool's definition Tool name 'updateTag' and description 'Update a tag' indicate modification of existing tag data.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
Update a tag. 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.
updateTag accepts 2 parameters: id, body. Required: id, body. 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 updateTag: 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.
updateTag 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 updateTag 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 updateTag. 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.
updateTag 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 →