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/io-github-malamutemayhem-unclick-mcp-server/raindrop-action.md
What raindrop_action does on UnClick
AI agents call raindrop_action to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
link | string | — | |
tags | array | — | |
title | string | — | |
action | string | Yes | |
search | string | — | |
api_key | string | — | |
raindrop_id | number | — | |
collection_id | number | — |
Parameters from the server's own tool schema.
Why raindrop_action is rated Low
Even though raindrop_action only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
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 read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
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 Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
raindrop_action accepts 8 parameters: link, tags, title, action, search, api_key, raindrop_id, collection_id. Required: action. 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 Read tool with low risk. Read-only tools are generally safe to allow by default.
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 (@unclick/mcp-server). 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.
This server
Across the catalogue