crow_shiori_delete
Delete a bookmark from Shiori. This is permanent and removes any cached content.
This record as markdown: /tools/kh0pper-crow/crow-shiori-delete.md
What crow_shiori_delete does on Crow
AI agents call crow_shiori_delete to permanently remove resources in Crow, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why crow_shiori_delete is rated Critical
This tool irreversibly removes bookmarks and their cached content from Shiori, matching the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone'. While a single bookmark deletion has limited blast radius (not critical), the permanent nature and explicit deletion semantics classify it as high severity Destructive rather than Write.
From the tool's definition Tool name explicitly states 'delete'; description says 'permanent' and 'removes any cached content', indicating irreversible deletion of data.
Attacks that exploit this kind of access
The rule that runs crow_shiori_delete 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_shiori_delete, this is the rule to start with:
crow_shiori_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crow_shiori_delete call is checked against it from then on.
Questions about crow_shiori_delete
Delete a bookmark from Shiori. This is permanent and removes any cached content. It is categorised as a Destructive tool in the Crow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Crow MCP server in PolicyLayer and add a rule for crow_shiori_delete: 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_shiori_delete 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 crow_shiori_delete 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_shiori_delete. 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_shiori_delete 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.
Across the catalogue