tag_manage

Perform tag management operations like renaming, merging, or deleting tags. Use this to maintain a clean tag structure.

Server Raindrop Io MCP Server kazuph/mcp-raindrop
Category Destructive
Risk class Critical
Parameters 00 required

What tag_manage does on Raindrop Io MCP Server

AI agents call tag_manage to permanently remove resources in Raindrop Io MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why tag_manage needs a policy

The tool explicitly supports deleting tags (irreversible removal) and merging tags (irreversibly collapses distinct tags into one). These destructive operations cannot be undone and could affect tags across many bookmarks simultaneously, giving it a high blast radius. Since destructive operations are present alongside write-like operations (renaming), the most severe category applies.

From the tool's definition 'deleting tags' and 'merging' tags — merging and deletion are irreversible operations that permanently remove or collapse tag data across bookmarks

Questions about tag_manage

What does the tag_manage tool do? +

Perform tag management operations like renaming, merging, or deleting tags. Use this to maintain a clean tag structure. It is categorised as a Destructive tool in the Raindrop Io MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on tag_manage? +

Register the Raindrop Io MCP Server MCP server in PolicyLayer and add a rule for tag_manage: 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 Raindrop Io MCP Server. Nothing to install.

What risk level is tag_manage? +

tag_manage is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit tag_manage? +

Yes. Add a rate_limit block to the tag_manage 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.

How do I block tag_manage completely? +

Set action: deny in the PolicyLayer policy for tag_manage. 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.

What MCP server provides tag_manage? +

tag_manage is provided by the Raindrop Io MCP Server MCP server (kazuph/mcp-raindrop). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.