wf_export_posts
Export all posts owned by the authenticated user as JSON. Useful for migration and backup.
This record as markdown: /tools/kh0pper-crow/wf-export-posts.md
What wf_export_posts does on Crow
AI agents call wf_export_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 wf_export_posts is rated Low
This tool retrieves and exports data (posts) as JSON for backup/migration purposes. It is a read/query operation with no side effects. However, it has medium severity because it exports ALL posts of the authenticated user, which could expose sensitive data if misused.
From the tool's definition Export all posts owned by the authenticated user as JSON. Useful for migration and backup.
Attacks that exploit this kind of access
The rule that runs wf_export_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_export_posts, this is the rule to start with:
wf_export_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 wf_export_posts call is checked against it from then on.
Questions about wf_export_posts
Export all posts owned by the authenticated user as JSON. Useful for migration and backup. 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 wf_export_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.
wf_export_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 wf_export_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 wf_export_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.
wf_export_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