collection_update · Raindrop Io MCP Server MCP

WHAT IT DOES

What collection_update does on Raindrop Io MCP Server

AI agents use collection_update to create or update resources in Raindrop Io MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Raindrop Io MCP Server environment.

WHY IT NEEDS A POLICY

Why collection_update needs a policy

The tool modifies collection metadata (title, visibility, view settings) without deleting data or executing arbitrary code. Changes are reversible through subsequent update calls, placing it in Write category. Severity is medium because misconfiguration could impact bookmark organization or access control, but no data is destroyed and no financial transactions occur.

From the tool's definition Tool description states 'Update collection properties like title, visibility, or view settings' and 'rename collections or change their configuration' — these are reversible modifications to metadata.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

collection_update Rate-limited

collection_update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "collection_update": {
      "limits": [
        {
          "counter": "collection_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Raindrop Io MCP Server, so you can run agents against it safely.

FAQ

Questions about collection_update

What does the collection_update tool do? +

Update collection properties like title, visibility, or view settings. Use this to rename collections or change their configuration. It is categorised as a Write tool in the Raindrop Io MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on collection_update? +

Register the Raindrop Io MCP Server MCP server in PolicyLayer and add a rule for collection_update: 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 collection_update? +

collection_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit collection_update? +

Yes. Add a rate_limit block to the collection_update 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 collection_update completely? +

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

collection_update 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.