Get the full content of a specific feed entry
AI agents call crow_miniflux_get_entry to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The verb 'Get' combined with 'full content of a specific feed entry' clearly describes a read-only operation that queries existing feed data. This is a retrieval operation with no destructive, state-changing, financial, or executable side effects. The Miniflux context (a feed reader) further confirms this is simply fetching pre-existing content.
From the tool's definition Tool name 'crow_miniflux_get_entry' and description 'Get the full content of a specific feed entry' indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access crow_miniflux_get_entry 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_get_entry:
{
"version": "1",
"default": "deny",
"tools": {
"crow_miniflux_get_entry": {}
}
} crow_miniflux_get_entry is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the full content of a specific feed entry. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for crow_miniflux_get_entry: 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_get_entry is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the crow_miniflux_get_entry 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_get_entry. 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_get_entry 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.