pf_feed
Fetch a timeline. home = follows; public = local+federated; local = this instance; notifications = mentions/likes/follows. Rate-limited: 60/hour.
This record as markdown: /tools/kh0pper-crow/pf-feed.md
What pf_feed does on Crow
AI agents call pf_feed 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 pf_feed is rated Low
This tool retrieves data from a federated social media timeline without creating, modifying, or deleting any content. It is purely a query operation that reads existing posts and notifications. The rate limiting further indicates it is a safe read operation. No side effects or data mutation occur.
From the tool's definition Tool name 'pf_feed' and description 'Fetch a timeline' with options for 'home', 'public', 'local', and 'notifications' — all retrieval operations with no modification or destructive capability. Rate-limited at 60/hour.
Attacks that exploit this kind of access
The rule that runs pf_feed 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 pf_feed, this is the rule to start with:
pf_feed 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 pf_feed call is checked against it from then on.
Questions about pf_feed
Fetch a timeline. home = follows; public = local+federated; local = this instance; notifications = mentions/likes/follows. Rate-limited: 60/hour. 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 pf_feed: 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.
pf_feed 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 pf_feed 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 pf_feed. 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.
pf_feed 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