List all tags or tags from a specific collection. Use this to understand the current tag structure before performing tag operations.
AI agents call tag_list to retrieve information from Raindrop Io MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
tag_list performs a read-only query of existing tags. It retrieves information about the tag structure without creating, modifying, or deleting any data. This is a low-risk reconnaissance operation typical of tag management systems.
From the tool's definition Tool description states 'List all tags or tags from a specific collection' — a pure retrieval operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
List all tags or tags from a specific collection. Use this to understand the current tag structure before performing tag operations. It is categorised as a Read tool in the Raindrop Io MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Raindrop Io MCP Server MCP server in PolicyLayer and add a rule for tag_list: 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.
tag_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the tag_list 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 tag_list. 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.
tag_list 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.
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 →