pf_mute_user

Mute an account (hide posts but still federate). 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-mute-user.md

WHAT IT DOES

What pf_mute_user does on Crow

AI agents use pf_mute_user 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_mute_user is rated Medium

Muting a user modifies account settings/relationships in a reversible way — it hides posts but does not delete or ban the account, and federation continues. This is a Write action (reversible social graph modification). The rate limit of 5/hour suggests it affects real federated accounts, raising the blast radius slightly if misused to silence legitimate users, hence medium severity.

From the tool's definition Mute an account (hide posts but still federate)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pf_mute_user Rate-limited

pf_mute_user 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_mute_user": {
      "limits": [
        {
          "counter": "pf_mute_user_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_mute_user call is checked against it from then on.

FAQ

Questions about pf_mute_user

What does the pf_mute_user tool do? +

Mute an account (hide posts but still federate). 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_mute_user? +

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

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

Can I rate-limit pf_mute_user? +

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

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

pf_mute_user 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

The MCP Attack Database →

Guides

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