readwise_import_recent · Readwise MCP Server MCP

WHAT IT DOES

What readwise_import_recent does on Readwise MCP Server

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

WHY IT NEEDS A POLICY

Why readwise_import_recent needs a policy

This tool writes data (imports documents) into the user's Readwise system, making it a Write-category operation. Severity is medium because while the operation is reversible (imported documents can be deleted), it modifies the user's data state and could potentially ingest unwanted or incorrect documents if an AI agent misuses the import parameters.

From the tool's definition The tool performs 'import' and explicitly mentions 'deduplication', which indicates it creates or modifies data by adding new documents to the user's Readwise collection.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

readwise_import_recent Rate-limited

readwise_import_recent 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": {
    "readwise_import_recent": {
      "limits": [
        {
          "counter": "readwise_import_recent_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 Readwise MCP Server, so you can run agents against it safely.

FAQ

Questions about readwise_import_recent

What does the readwise_import_recent tool do? +

Import recent documents since last import with deduplication. It is categorised as a Write tool in the Readwise 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 readwise_import_recent? +

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

What risk level is readwise_import_recent? +

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

Can I rate-limit readwise_import_recent? +

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

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

readwise_import_recent is provided by the Readwise MCP Server MCP server (ngpestelos/readwise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.