Block an entire remote instance (admin, instance-scope blocklist — hides all accounts + videos from that domain for every user on this server). QUEUED — requires operator confirmation in the Nest panel within 72h.
AI agents call pt_block_server to permanently remove resources in Crow — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool enacts an instance-wide block that irreversibly hides all content and accounts from a remote domain for every user on the server. While it is queued for operator confirmation, the action itself is broadly destructive in scope — affecting all users server-wide and suppressing entire swaths of federated content.
From the tool's definition Block an entire remote instance...hides all accounts + videos from that domain for every user on this server
Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation
Documented attack patterns abuse exactly the kind of access pt_block_server 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_server:
{
"version": "1",
"default": "deny",
"hide": [
"pt_block_server"
]
}pt_block_server disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Block an entire remote instance (admin, instance-scope blocklist — hides all accounts + videos from that domain for every user on this server). QUEUED — requires operator confirmation in the Nest panel within 72h. It is categorised as a Destructive tool in the Crow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Crow MCP server in PolicyLayer and add a rule for pt_block_server: 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_server is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the pt_block_server 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_server. 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_server 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.