Medium Risk

mastodon_mute_user

Mute an account (hide posts but still federate). Rate-limited: 5/hour.

How to control mastodon_mute_user ↓

What mastodon_mute_user does on Crow

AI agents use mastodon_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.

Medium Risk

Why mastodon_mute_user needs a policy

Muting a user modifies the relationship/visibility state between accounts — it is a reversible social action (can be unmuted) that changes data on the platform. It does not delete content or execute code, making Write the appropriate category. The rate limit of 5/hour and the potential to affect user experience elevates severity to medium.

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

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

How to control mastodon_mute_user

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 mastodon_mute_user:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "mastodon_mute_user": {
      "limits": [
        {
          "counter": "mastodon_mute_user_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  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.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about mastodon_mute_user

What does the mastodon_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 mastodon_mute_user? +

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

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

Can I rate-limit mastodon_mute_user? +

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

Set action: deny in the PolicyLayer policy for mastodon_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 mastodon_mute_user? +

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

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.