Mark entries as read. Pass specific entry IDs or
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.
The tool creates or modifies data (entry read status) in a reversible manner. It does not delete, execute code, or perform financial operations. This is a typical Write operation—changing metadata state without destructive consequences. Severity is low because misuse would only affect feed read status with no blast radius beyond the user's project management data.
From the tool's definition Tool name contains 'mark_read' and description states 'Mark entries as read.' This modifies the read/unread status of feed entries, which is a reversible state change.
Documented attack patterns abuse exactly the kind of access crow_miniflux_mark_read gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crow_miniflux_mark_read:
{
"version": "1",
"default": "deny",
"tools": {
"crow_miniflux_mark_read": {
"limits": [
{
"counter": "crow_miniflux_mark_read_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.