Low Risk

pf_status

Report Pixelfed instance health: reachability, version, stats, federation peer count, authenticated account.

How to control pf_status ↓

What pf_status does on Crow

AI agents call pf_status to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why pf_status needs a policy

This tool retrieves and queries system status information about a Pixelfed instance. It performs no destructive, financial, or state-changing operations. It does not execute arbitrary code or commands. The severity is low because the information exposed (health metrics, federation status) is typically non-sensitive operational data that administrators already monitor.

From the tool's definition Tool reports instance health metrics including 'reachability, version, stats, federation peer count, authenticated account' — all read-only status queries with no modification or side effects.

Documented attack patterns abuse exactly the kind of access pf_status gives an agent:

How to control pf_status

PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for pf_status:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "pf_status": {}
  }
}

pf_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Crow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about pf_status

What does the pf_status tool do? +

Report Pixelfed instance health: reachability, version, stats, federation peer count, authenticated account. 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 pf_status? +

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

What risk level is pf_status? +

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

Can I rate-limit pf_status? +

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

How do I block pf_status completely? +

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

What MCP server provides pf_status? +

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

Enforce policy on every Crow tool call.

Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.