Clear state file (optionally preserve synced_ranges)
AI agents call readwise_reset_state to permanently remove resources in Readwise MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool clears the state file, which contains synchronization state (synced_ranges and other tracking data). Losing this state cannot be easily undone and would affect the ability to track what has been synced, potentially causing data re-imports or loss of deduplication history. The optional preservation of synced_ranges slightly mitigates but does not eliminate the destructive nature.
From the tool's definition 'Clear state file' — clearing/resetting state is an irreversible destructive action that removes stored synchronization state
Attacks that exploit this kind of access
Clear state file (optionally preserve synced_ranges). It is categorised as a Destructive tool in the Readwise MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Readwise MCP Server MCP server in PolicyLayer and add a rule for readwise_reset_state: 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.
readwise_reset_state is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the readwise_reset_state 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_reset_state. 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_reset_state 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →