This record as markdown: /tools/kh0pper-crow/crow-list-posts.md
What crow_list_posts does on Crow
AI agents call crow_list_posts to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why crow_list_posts is rated Low
The tool performs a query/list operation to retrieve blog posts based on filters. This is a read-only operation with no side effects, reversible modifications, code execution, data destruction, or financial impact. The blast radius of misuse is minimal—at worst, an AI agent could retrieve unintended posts, but no data would be modified, deleted, or compromised.
From the tool's definition Tool name 'crow_list_posts' and description 'List blog posts with filtering' indicate data retrieval operations with no modification or deletion of data.
Attacks that exploit this kind of access
The rule that runs crow_list_posts 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_list_posts, this is the rule to start with:
crow_list_posts is read-only, so it stays allowed. 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_list_posts call is checked against it from then on.
Questions about crow_list_posts
List blog posts with filtering. 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_list_posts: 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_list_posts 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_list_posts 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_list_posts. 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_list_posts 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