raindrop_action
Perform a Raindrop.io action: search_raindrops, get_collection_raindrops, get_raindrop_collections, create_raindrop, get_raindrop, delete_raindrop.
This record as markdown: /tools/creativelead-unclick/raindrop-action.md
What raindrop_action does on UnClick
AI agents call raindrop_action to permanently remove resources in UnClick, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
link | string | — | |
tags | array | — | |
title | string | — | |
action | string | — | |
search | string | — | |
api_key | string | — | |
raindrop_id | number | — | |
collection_id | number | — |
Parameters from the server's own tool schema.
Why raindrop_action is rated Critical
The tool bundles multiple operations including 'delete_raindrop', which irreversibly removes a bookmark. Since the most severe applicable category applies and deletion is irreversible, this is classified as Destructive. The high severity reflects that an AI agent could delete bookmarks/collections that cannot be recovered.
From the tool's definition Perform a Raindrop.io action: search_raindrops, get_collection_raindrops, get_raindrop_collections, create_raindrop, get_raindrop, delete_raindrop
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs raindrop_action safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For raindrop_action, this is the rule to start with:
raindrop_action is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every raindrop_action call is checked against it from then on.
Questions about raindrop_action
Perform a Raindrop.io action: search_raindrops, get_collection_raindrops, get_raindrop_collections, create_raindrop, get_raindrop, delete_raindrop. It is categorised as a Destructive tool in the UnClick MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
raindrop_action accepts 8 parameters: link, tags, title, action, search, api_key, raindrop_id, collection_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for raindrop_action: 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 UnClick. Nothing to install.
raindrop_action 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 raindrop_action 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 raindrop_action. 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.
raindrop_action is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
Across the catalogue