crow_miniflux_mark_read
Mark entries as read. Pass specific entry IDs or
This record as markdown: /tools/kh0pper-crow/crow-miniflux-mark-read.md
What crow_miniflux_mark_read does on Crow
AI agents use crow_miniflux_mark_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_miniflux_mark_read is rated Medium
This tool modifies data (entry read status) in a reversible manner, which is characteristic of Write operations. While a user could mark many entries as read, this action is easily undone by marking them unread. The blast radius is minimal as it only affects the user's reading state and does not cause data loss, execute arbitrary code, or have financial implications.
From the tool's definition Tool name 'mark_read' and description 'Mark entries as read' indicate a state modification operation on feed entries.
Attacks that exploit this kind of access
The rule that runs crow_miniflux_mark_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_miniflux_mark_read, this is the rule to start with:
crow_miniflux_mark_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_miniflux_mark_read call is checked against it from then on.
Questions about crow_miniflux_mark_read
Mark entries as read. Pass specific entry IDs or. 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_miniflux_mark_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_miniflux_mark_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_miniflux_mark_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_miniflux_mark_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_miniflux_mark_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