Delete a tag Soft-deletes the tag by setting deletedAt. Existing note-tag associations are not removed.
AI agents call deleteTag to permanently remove resources in Memnote — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes |
Parameters from the server's own tool schema.
Although implemented as a soft-delete rather than hard deletion, the tool irreversibly removes a tag from active use. Users cannot undo the deletion through normal operations, and existing associations become invalid. This fits the Destructive category as an action that cannot be easily reversed.
From the tool's definition Tool name 'deleteTag' combined with description 'Delete a tag' indicates permanent removal. The note adds it is a soft-delete (setting deletedAt rather than hard removal), which reduces irreversibility slightly, but the tag is removed from active use and…
Attacks that exploit this kind of access
Delete a tag Soft-deletes the tag by setting deletedAt. Existing note-tag associations are not removed. It is categorised as a Destructive tool in the Memnote MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
deleteTag accepts 1 parameter: id. Required: id. 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 deleteTag: 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.
deleteTag is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deleteTag 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 deleteTag. 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.
deleteTag 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 →