list_readwise_documents_by_filters

THE RISK

Low Risk

Why list_readwise_documents_by_filters needs a policy

The tool lists/retrieves Readwise documents based on filter criteria—a non-destructive query operation. It does not modify, delete, or execute external actions. Despite the empty description lowering confidence slightly, the naming convention and sibling context confirm this is a Read operation with low blast radius.

From the tool's definition Tool name 'list_readwise_documents_by_filters' indicates a query/retrieval operation. Server description confirms it accesses documents 'programmatically', and sibling tools include other read operations (find_readwise_documents_by_names,…

Documented attack patterns abuse exactly the kind of access list_readwise_documents_by_filters gives an agent:

POLICY

How to control list_readwise_documents_by_filters

PolicyLayer is an MCP gateway — it sits between your AI agents and Kiseki-Labs-Readwise-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for list_readwise_documents_by_filters:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_readwise_documents_by_filters": {}
  }
}

list_readwise_documents_by_filters is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Kiseki-Labs-Readwise-MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Kiseki-Labs-Readwise-MCP tools

Destructive delete_readwise_tag Remove a tag from a Readwise highlight or book. Write add_readwise_tag add_readwise_tag Write update_readwise_tag update_readwise_tag Read find_readwise_documents_by_names find_readwise_documents_by_names Read get_readwise_highlights_by_document_ids get_readwise_highlights_by_document_ids Read get_readwise_highlights_by_filters get_readwise_highlights_by_filters Read get_readwise_tags get_readwise_tags

All 8 Kiseki-Labs-Readwise-MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about list_readwise_documents_by_filters

What does the list_readwise_documents_by_filters tool do? +

list_readwise_documents_by_filters. It is categorised as a Read tool in the Kiseki-Labs-Readwise-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_readwise_documents_by_filters? +

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

What risk level is list_readwise_documents_by_filters? +

list_readwise_documents_by_filters is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_readwise_documents_by_filters? +

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

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

list_readwise_documents_by_filters is provided by the Kiseki-Labs-Readwise- MCP server (kiseki-technologies/kiseki-labs-readwise-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Kiseki-Labs-Readwise-MCP tool call.

Start from Kiseki-Labs-Readwise-MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →