mastodon_block_user
Block an account (hide their posts + block DMs from them). Rate-limited: 5/hour.
This record as markdown: /tools/kh0pper-crow/mastodon-block-user.md
What mastodon_block_user does on Crow
AI agents use mastodon_block_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.
Why mastodon_block_user is rated Medium
Blocking a user modifies the relationship state between accounts (creates a block record), which is a reversible write action. It does not delete data, move money, or execute code. The action can be undone by unblocking. Severity is medium because misuse could affect user relationships and communications at scale, but it is rate-limited to 5/hour.
From the tool's definition Block an account (hide their posts + block DMs from them)
Attacks that exploit this kind of access
The rule that runs mastodon_block_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 mastodon_block_user, this is the rule to start with:
mastodon_block_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every mastodon_block_user call is checked against it from then on.
Questions about mastodon_block_user
Block an account (hide their posts + block DMs from them). 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.
Register the Crow MCP server in PolicyLayer and add a rule for mastodon_block_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.
mastodon_block_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mastodon_block_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.
Set action: deny in the PolicyLayer policy for mastodon_block_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.
mastodon_block_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.
More on Crow, and thousands of servers like it.
This server
Across the catalogue