pf_post_photo

Upload a photo and publish it as a status. Uploads via POST /api/v1/media then POST /api/v1/statuses. Pass file_path OR file_base64+filename. Rate-limited: 10/hour.

SERVERCrow SOURCEkh0pper/crow

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/pf-post-photo.md

WHAT IT DOES

What pf_post_photo does on Crow

AI agents use pf_post_photo to create or update resources in Crow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.

RISK

Why pf_post_photo is rated Medium

This tool creates new data (media uploads and status posts) in a reversible manner. While it performs public actions on behalf of the user, the effects are not destructive (can be deleted), not financial, and not executing arbitrary code.

From the tool's definition Tool description states 'Upload a photo and publish it as a status' using POST requests to /api/v1/media and /api/v1/statuses, which are create operations that modify data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pf_post_photo Rate-limited

pf_post_photo stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pf_post_photo": {
      "limits": [
        {
          "counter": "pf_post_photo_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about pf_post_photo

What does the pf_post_photo tool do? +

Upload a photo and publish it as a status. Uploads via POST /api/v1/media then POST /api/v1/statuses. Pass file_path OR file_base64+filename. Rate-limited: 10/hour. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pf_post_photo? +

Register the Crow MCP server in PolicyLayer and add a rule for pf_post_photo: 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_post_photo? +

pf_post_photo is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pf_post_photo? +

Yes. Add a rate_limit block to the pf_post_photo 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_post_photo completely? +

Set action: deny in the PolicyLayer policy for pf_post_photo. 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_post_photo? +

pf_post_photo 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

team_manager_post_blackboard on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →