crow_kavita_want_to_read
Manage the Kavita want-to-read list: add, remove, or list series
This record as markdown: /tools/kh0pper-crow/crow-kavita-want-to-read.md
What crow_kavita_want_to_read does on Crow
AI agents use crow_kavita_want_to_read to create or update resources in Crow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.
Why crow_kavita_want_to_read is rated Medium
The tool can add or remove entries from a want-to-read list, which constitutes reversible data modification (Write). The 'list' action is read-only, but since the tool also supports add/remove, the most severe applicable category is Write. Severity is medium as it modifies user reading list data but has limited blast radius beyond the Kavita library management system.
From the tool's definition Manage the Kavita want-to-read list: add, remove, or list series
Attacks that exploit this kind of access
The rule that runs crow_kavita_want_to_read safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_kavita_want_to_read, this is the rule to start with:
crow_kavita_want_to_read 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 Crow, apply this rule, and every crow_kavita_want_to_read call is checked against it from then on.
Questions about crow_kavita_want_to_read
Manage the Kavita want-to-read list: add, remove, or list series. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Crow MCP server in PolicyLayer and add a rule for crow_kavita_want_to_read: 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 Crow. Nothing to install.
crow_kavita_want_to_read 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 crow_kavita_want_to_read 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 crow_kavita_want_to_read. 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.
crow_kavita_want_to_read is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
This server
Across the catalogue