wf_list_posts

List posts in a collection (public endpoint — no auth required). Paginated.

SERVERCrow SOURCEkh0pper/crow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/wf-list-posts.md

WHAT IT DOES

What wf_list_posts does on Crow

AI agents call wf_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.

RISK

Why wf_list_posts is rated Low

The tool retrieves data from a collection without modifying, deleting, or executing external operations. It is publicly accessible and paginated, indicating standard data retrieval. The 'list' verb and 'public endpoint' language confirm it is informational only.

From the tool's definition Tool name and description explicitly state 'List posts' and 'public endpoint — no auth required'. This is a query/retrieval operation with no side effects, matching the Read category definition.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wf_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 wf_list_posts, this is the rule to start with:

wf_list_posts Allowed

wf_list_posts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wf_list_posts": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every wf_list_posts call is checked against it from then on.

FAQ

Questions about wf_list_posts

What does the wf_list_posts tool do? +

List posts in a collection (public endpoint — no auth required). Paginated. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on wf_list_posts? +

Register the Crow MCP server in PolicyLayer and add a rule for wf_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.

What risk level is wf_list_posts? +

wf_list_posts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit wf_list_posts? +

Yes. Add a rate_limit block to the wf_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.

How do I block wf_list_posts completely? +

Set action: deny in the PolicyLayer policy for wf_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.

What MCP server provides wf_list_posts? +

wf_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.

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →