pf_report_remote

File a moderation report to a remote server about an account. Rate-limited: 5/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-report-remote.md

WHAT IT DOES

What pf_report_remote does on Crow

AI agents use pf_report_remote 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_report_remote is rated Medium

This tool submits a moderation report to a remote server, which creates a new record/action on that server. It is a Write operation (creating a report) with cross-server effects. While it could influence moderation outcomes for an account, it doesn't directly delete or modify data irreversibly — a report is a submission that triggers a review process.

From the tool's definition File a moderation report to a remote server about an account

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pf_report_remote Rate-limited

pf_report_remote 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_report_remote": {
      "limits": [
        {
          "counter": "pf_report_remote_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_report_remote call is checked against it from then on.

FAQ

Questions about pf_report_remote

What does the pf_report_remote tool do? +

File a moderation report to a remote server about an account. Rate-limited: 5/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_report_remote? +

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

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

Can I rate-limit pf_report_remote? +

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

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

pf_report_remote 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

generate_devtools_report on Percepta MCP Server →generate_forensic_report on Android Forensics ADB MCP Server → The MCP Attack Database →

Guides

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