readwise_action
Perform a Readwise action: get_readwise_highlights, get_readwise_books, get_daily_review, search_highlights, create_highlight.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/readwise-action.md
What readwise_action does on UnClick
AI agents use readwise_action to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | number | — | |
query | string | — | |
action | string | Yes | |
api_key | string | — | |
book_id | number | — | |
highlights | array | — |
Parameters from the server's own tool schema.
Why readwise_action is rated Medium
The tool supports multiple operations including 'create_highlight', which writes new data to Readwise. Since the tool spans Read and Write categories, the most severe applicable category is Write. The blast radius is medium since creating unwanted highlights is reversible but could pollute a user's reading data.
From the tool's definition Perform a Readwise action: get_readwise_highlights, get_readwise_books, get_daily_review, search_highlights, create_highlight
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs readwise_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 readwise_action, this is the rule to start with:
readwise_action 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.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every readwise_action call is checked against it from then on.
Questions about readwise_action
Perform a Readwise action: get_readwise_highlights, get_readwise_books, get_daily_review, search_highlights, create_highlight. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
readwise_action accepts 6 parameters: page, query, action, api_key, book_id, highlights. 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 readwise_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.
readwise_action is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the readwise_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 readwise_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.
readwise_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