Block an account (hide their videos + comments). Rate-limited: 5/hour.
AI agents use pt_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.
Blocking a user modifies account relationship state and suppresses their content visibility, which is a reversible write action. However, the blast radius is high because it affects another user's presence and content visibility across a platform, and could be misused to systematically silence users. It is not Destructive because the block can presumably be undone.
From the tool's definition Block an account (hide their videos + comments)
Documented attack patterns abuse exactly the kind of access pt_block_user gives an agent:
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 pt_block_user:
{
"version": "1",
"default": "deny",
"tools": {
"pt_block_user": {
"limits": [
{
"counter": "pt_block_user_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} pt_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.
Free to start. No card required.
Block an account (hide their videos + comments). 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 pt_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.
pt_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 pt_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 pt_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.
pt_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.
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.