pf_import_blocklist
Import a domain blocklist (IFTAS / Bad Space / custom URL). QUEUED — requires operator confirmation. Rate-limited: 2/hour.
This record as markdown: /tools/kh0pper-crow/pf-import-blocklist.md
What pf_import_blocklist does on Crow
AI agents use pf_import_blocklist 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 pf_import_blocklist is rated Medium
This tool creates or modifies filtering rules/data by importing blocklists from external sources (IFTAS, Bad Space, or custom URLs). While reversible (blocklists can be removed or updated), it durably changes system configuration. It is not Read (actively modifies state), not Destructive (the import itself is reversible), not Execute (doesn't run arbitrary code based on arguments), and not Financial.
From the tool's definition Tool name 'pf_import_blocklist' and description 'Import a domain blocklist' indicates the tool creates or modifies blocklist data.
Attacks that exploit this kind of access
The rule that runs pf_import_blocklist 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_import_blocklist, this is the rule to start with:
pf_import_blocklist 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 pf_import_blocklist call is checked against it from then on.
Questions about pf_import_blocklist
Import a domain blocklist (IFTAS / Bad Space / custom URL). QUEUED — requires operator confirmation. Rate-limited: 2/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 pf_import_blocklist: 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.
pf_import_blocklist 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 pf_import_blocklist 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 pf_import_blocklist. 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.
pf_import_blocklist 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