wf_status
Report WriteFreely instance health: reachability, federation status, authenticated user, collection count.
This record as markdown: /tools/kh0pper-crow/wf-status.md
What wf_status does on Crow
AI agents call wf_status 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_status is rated Low
wf_status queries the status of a WriteFreely instance and returns information about its operational state. This is a read-only operation that retrieves data without side effects. The tool does not create, modify, delete, execute arbitrary operations, or involve financial transactions. The severity is low because disclosing health status information poses minimal risk compared to other categories.
From the tool's definition The tool 'report[s]' health metrics including 'reachability, federation status, authenticated user, collection count' — these are observational queries with no modification of state.
Attacks that exploit this kind of access
The rule that runs wf_status 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_status, this is the rule to start with:
wf_status 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_status call is checked against it from then on.
Questions about wf_status
Report WriteFreely instance health: reachability, federation status, authenticated user, collection count. 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_status: 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_status 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_status 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_status. 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_status 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